Flow Designer wait for multiple tasks to complete - Service Catalog

Patrick Slatter
Tera Guru

Morning!

 

Looking for assistance in how to complete the following.,

Wait for multiple tasks to complete before proceeding in flow. I have 3 catalog tasks that need to generate at the same time, then the flow should not proceed until all 3 of those are complete. 

 

The wait for conditions either seems sequesntial or time based opposed to the group of tasks all being complete before proceeding to the next item. 

 

Any guidance would be greatly appriciated!

 

1 ACCEPTED SOLUTION

You can put steps 9 through 11 in a "do the following in parallel" then check the "Wait" on each. This should allow each one to generate and then wait for them all to close.

 

ElijahAromola_1-1673445753580.png

 

 

View solution in original post

9 REPLIES 9

You can put steps 9 through 11 in a "do the following in parallel" then check the "Wait" on each. This should allow each one to generate and then wait for them all to close.

 

ElijahAromola_1-1673445753580.png

 

 

This worked and eliminated the need for a loop.

 

Thank you!

Curious, how to do you account for each state of these multiple catalog tasks. Say these are all child tasks under one RITM. How, if at all, do you set the state of the RITM based on the states of these child tasks. Say Task1 and Task2 are marked closed incomplete, and Task3 is marked closed complete. Currently we have our RITM closing based on the state of the ScTask, just wondering if this could work with multiple tasks under a single RITM. 

 

Thanks, 

 

Cobee

That may work if you now the exact static tasks that are to be created but how about when the tasks are dynamically created as part of a Loop lookup? 


G24
Kilo Sage

If you want a solution which also allows Manual tasks to be created "on the fly", and still waits for all of those tasks to be completed, you could try a "SubFlow" solution, such as this:

https://www.servicenow.com/community/developer-forum/flow-how-to-properly-wait-for-all-sc-task-recor... 

Not especially easy to implement though, I will admit.