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]

Adding a before update rule on the table and having the check, could work. If the check is true, setAbortAction. That would stop triggering the subsequent workflows and business rule action.

But if you adopt the above approach, you are not addressing the design issue and looking for a workaround.

[KristinaB]

Thanks for the tip Kalaiarasan. We'll have to look into this but pretty beginner here.

[HugoFirst]

Did you try the Join?   We use it to wait for multiple tasks to complete before moving on.

Here's an example: If you use the incomplete exit, the workflow will progress if any ONE of the tasks complete.

If you use the complete exit, them it waits until ALL tasks have complete.

[KristinaB]

Tried this one Steve but found that it ignored any manually created tasks on the RITM. If the task was triggered from within the workflow, then it works, as long as there is only one branch. Found that we would need to add mutiple joins for each branch in the wf. Here's a sample wf