Alternative to workflow wait for condition

[KristinaB]

Hi there,

We currently have a wait for all tasks to close condition in all of our workflows and are looking for some ideas on how to streamline/centralize this. We originally were using a SUB flow with would be added to each workflow to ensure that it would wait for all TASKs to close before moving on. We are encountering issues with our Geneva testing and have determined that it is due to the SUB flows. We have 100+ workflows to update. Has any one used a business rule or something to centralize this check in the workflow?

Thanks....

[Kalaiarasan Pus]

Check this approach.

Condition Activities - ServiceNow Wiki

It will handle all tasks plus manual ones too.

[KristinaB]

Thanks Kalaiarasan. We are already familiar with these conditions but are exploring other options so that we don't need to add an activity to every workflow. Thanks for all your suggestions. Much appreciated.

[HugoFirst]

Whoops!   I must not have explained it very well.   You should have only ONE join box, not three.

You route the exit lines from each of the preceding tasks ( and "Set Values" script ) to that one join box.

The exit of that one Join box will go to the "Set Value" box that sets the stage to completed.

[KristinaB]

Yeah we tried that but with the different branches, it was waiting for all tasks to complete even if they were never going to be triggered. Hope that makes sense.

[Uncle Rob · Accepted solution]

Any time you're going to deal with manual sc_tasks parallel to a workflow you've got to use Kalai's link (section 4.4) at the end.
Either that or be *VERY* good with business rules that rigidly control whether or not a given SC_Task updates or does not update a workflow for a parent RITM.