Current item is not passed as a context to the workflow

[DianaT]

Hello experts

Can you explain the following behavior - is it a bug or an intended scenario?
If it is intended - what’s the logic behind?

I can define the Actions in Items in the Collection.
For example - I need a Delete action.

The inconsistency is when I call this action for a specific item, as on the screen.
If I call an action - it works on the actual row as expected
But if I activate a Workflow for this action - it does not pass the actual item as the context row to the workflow. An the workflow runs on an arbitrary selected row.

Is it an expected behavior? or it a bug?

Many thanks
Diana

[MaximeBaker]

Are you using the right trigger? User interaction?

[DianaT]

I suppose yes.

The workflow is triggered for the Delete action in the Item menu

if I check details in the workflow - it shows the details for some another item (i suppose the first row in the table)

I found a workaround for my specific case but this behaviour just looked suspicious )

D

[ThinhDinh]

@DianaT

But if I activate a Workflow for this action - it does not pass the actual item as the context row to the workflow. An the workflow runs on an arbitrary selected row.

You have to pass a context to the workflow (I assume you’re triggering a manual workflow). In most cases, this should be the rowID, then you do a loop to find that row and delete the row.

Though, you shouldn’t do that, just use the Delete Row action on a user-triggered workflow like you have done.