Wait until selection

Hi ‌

Is it possible to have the original workflow stop before this point and have a workflow to run on edit of the list item with either a condition or run if actions for the 2 possible outcomes?

‌ ‌

Thanks Paul Crawford for your reply.

Assuming I created another workflow to check the value of that field and run corresponding action thereafter; how will I configure this workflow to run only when this particular field is updated?

Setting the WF to run on edit will trigger it whenever any column in the list is updated knowing that several edits will take place before reaching this stage.

Thanks

Hi Hassan Dhainy‌

Unfortunately you cant have a conditional start in O365 so you are correct it would have to run every time the item is updated, but the run if means that only if that condition is true then the actions after will take place.

So the run if would be configured:

When - List Lookup

Source - Current Item

Field - Status

Equals - Confirmed

This would run the confirmed actions

When - List Lookup

Source - Current Item

Field - Status

Equals - Cancelled

This would run the cancelled actions

The corresponding actions would only happen when the field values matched.

The only thing to take in to account would be if there could be any other edits after the status change had taken place to set it to either Confirmed or Cancelled meaning the workflow would start and these conditions would be met.

Hope this helps

I will give it a try tomorrow morning and let you the outcome.

Hi ‌

sounds like an excellent solution. Not having had lots of use of nintex O365 I was unaware of the parallel block.  Hopefully we have helped ‌

‌, have you considered assigning a task to the user?

it as well stops workflow execution and waits until the task is responded.

with the task approach, you likely wouldn't need 'Pending' response at all, since until the task is responded it is still considered to be 'pending'. so one action less needed to be performed by your users.

Tom Castiglia  the parallel action seems interesting and I am testing right now and give my feedback here.

Paul Crawford the solution you advised is also good but requires the second workflow which runs on list update to be executed more than 10 times at least since the list will be updated several times during the process.

Marian Hatala the assign a task was the first thing I thought about but it will not suite the current job process which I  can summary as below:

The use sends the quotation to client and waits for a reply; during this, the status is pending with a comment area for user to update whenever he gets a reply from client, stating the reason for being pending. The process of updating this text box should continue until the client finally reply with either confirming the quotation or cancelling it.

Thus the task for confirming (or cancelling) has no specific time to be assigned as it depends on client reply which might be after 1 week, 2 weeks or 1 month.

Thank you all for the effective help.

Hi Hassan – just curious, did the parallel action approach work for you?

Yes Tom, apparently the parallel action did the trick. I tested it on one example and the process worked as it should.

Already marked your answer as correct answer.

Many thanks 

Such a simple but efficient solution....and it works