Branch Join Action: Workflow vs Flow Design

[terrieb]

We have a few Onboarding/Offboarding catalog items that have specific back end tasks that need to be completed before tasks for application access and IT equipment tasks are created.  

We built these a few years back and created Workflows to do this type of operation using the Branch/Join on the additional tasks after the first few tasks are completed.  This works great, because there is no set due dates or requirements on when the additional tasks are to be completed and, most important, the Request/RITM does not go to Closed Complete state until ALL the tasks are closed.

How can this type of action be recreated using Flow Design.  I put a "wait for condition" after the first initial tasks before the additional tasks are created, which works just fine, but using another "wait for condition" on the last additional task is not working because sometimes that task is completed before other additional tasks, so the Request/RITM goes to closed complete state with open (orphan) tasks.  I even tried checking the "wait" box on the last task, but it still creates with all the other tasks instead.

I have tried parallel flows and sub flows, but still getting the same result.

Any suggestions?

[SwarnadeepNandy]

Hello @terrieb,

One possible way to do this is to use a combination of parallel flows, subflows, and conditions. Here is a high-level overview of the steps:

• Create a main flow attach it to the catalog item that triggers on the request/RITM creation and sets the state to “In Progress”.
• In the main flow, add a parallel flow action and configure it to run two subflows: one for the initial tasks and one for the additional tasks.
• In the subflow for the initial tasks, create the tasks using the “Create Task” action and set the “Wait” option to true. This will make the subflow wait until all the initial tasks are closed before proceeding.
• In the subflow for the additional tasks, add a “Wait for Condition” action and configure it to wait until all the initial tasks are closed. You can use a condition like “Task [Parent] [is] [current record]” and “Task [State] [is] [Closed Complete]” with an “AND” operator. This will make the subflow wait until all the initial tasks are closed before creating the additional tasks.
• After the “Wait for Condition” action, create the additional tasks using the “Create Task” action and set the “Wait” option to true. This will make the subflow wait until all the additional tasks are closed before proceeding.
• In the main flow, after the parallel flow action, add a condition to check if all the tasks are closed. You can use a similar condition as above, but with an “OR” operator. This will make the main flow wait until all the tasks are closed before proceeding.
• After the condition, add an action to set the state of the request/RITM to “Closed Complete”.

This is one possible way to recreate your workflow using flow designer. You can also use other actions or conditions as needed, such as setting variables, sending notifications, updating records, etc.

Hope this helps.

Kind Regards,

Swarnadeep Nandy

[terrieb]

Thanks!

Will try this and if it works as we hope, will mark this "Accept as Solution"

[terrieb]

I followed your steps and while the tasks are waiting to be created after initial required task is closed complete and then they all create as they should, (used the Parallel for that action), once all the tasks are closed, the Request/RITM not changing to Closed Complete.

I added in the IF action and created 3 conditions for the 3 total tasks, but am I missing a step or doing something wrong in this Flow Design?

[SwarnadeepNandy]

Hello @terrieb,

Try something like this.

Kind Regards,

Swarnadeep Nandy