Sub-flows are often used for re-useable pieces of logic. For example, you might have a solution in which multiple flows need to ask for a date of birth. In that case, one single sub-flow that asks for the date of birth can be used. This sub-flow can then be called by any flow that needs the user's date of birth.
Unlike regular flows, sub-flows are not triggered by a user input. In fact, sub-flows do not have triggers at all. Sub-flows can only be activated when linked to from other flows.
Once the sub-flow has finished processing, execution will be handed back to the parent flow. One flow can link to multiple sub-flows, which will behave as if they were part of the parent flow. Sub-flows can also link to other subflows. When linking to a sub-flow you can specify which variables can be transferred back and forth. If an output in the sub-flow uses a revisitability limit and that limit is exceeded, the sub-flow and all calling flows are dropped.
Sub-flows are created in the same way as regular flows. However, to turn a regular flow into a sub-flow, click the 'Sub-Flow' icon in the 'Flow Entry' group of the ribbon when editing a flow. This will remove the trigger and turn it into a sub-flow entry point.
Was this page helpful?