Dynamic flows flow logic
-
- UpdatedAug 1, 2024
- 3 minutes to read
- Xanadu
- Create Workflows
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
The Dynamic Flow flow logic calls a flow or subflow during runtime by using the data that you specify during the flow design. You can use Dynamic Flow to select which flow to run when multiple flows have similar names or purposes.
- Creates and publishes a flow or subflow to use as a template.
- Adds Dynamic Flow to a parent flow.
- Selects the flow template for Dynamic Flow.
- Enters the flow name for Dynamic Flow.
- Enters the required inputs specified by the flow template.
Dynamic flow templates
The template for Dynamic Flow can be a flow or a subflow. The template's inputs must match the inputs of any flow or subflow that you call dynamically. An input matches when it has the same Label and Name field values in each flow or subflow.
After you build a template, consider copying it to create similarly named and similarly performing flows or subflows. Make sure that you name each flow or subflow with a standard naming convention that can be generated by Dynamic Flow. For more information on creating a template for Dynamic Flow, see Getting started with Dynamic Flow and Get Flow Outputs.
Inputs
The following inputs always appear when you add the Dynamic Flow flow logic to a flow.
| Input | Description |
|---|---|
| Flow Template | Template whose inputs the dynamic flow copies and displays. The inputs for the template must match the inputs of the subflow that you want to run. |
| Flow | Name or Sys ID of the flow or subflow that you want to run. Flow names must be the display name not the flow internal name. For example, enter the name My dynamic flow not my_dynamic_flow. Generate a flow or subflow name dynamically by entering a string and concatenating it with data pill values. You can call a flow or subflow that is associated with another application scope by entering a scope-name.flow-name format. The user running the flow or subflow must have access to the application scopes that you specify. If you do not specify an application scope, the dynamic flow runs in the parent flow's scope. Note: If the system can't find the flow or subflow, it skips the Dynamic
Flow flow logic step and logs an error message. |
| Wait for completion | Option to force the parent flow to wait until the dynamic flow finishes running before proceeding with the next action. |
Get flow outputs
- Adds a Dynamic Flow to a flow.
- Adds Get Flow Outputs after the dynamic flow.
- Specifies the value for the Context input by clicking the data pill
picker (
) and selecting .
For more information on using Get Flow Outputs, see Getting started with Dynamic Flow and Get Flow Outputs.
General guidelines
- Use dynamic flows if you have multiple subflows with similar functionality
- Dynamic flows let you compartmentalize your processes by applying a template to handle the inputs of multiple similar subflows. Compartmentalization lets you distinguish between subflows that perform similar functions, such as subflows for IntegrationHub spokes.
- Ensure dynamically called subflow inputs match template flow inputs
- The system throws an error and the main flow can't run properly when the inputs of a dynamic flow and flow template don't match.
- Use the correct context when getting flow outputs
- A context record uniquely identifies the flow run. If you run a dynamic flow multiple times, there are multiple context records to choose from. When you use dynamic flow multiple times within a flow, make sure to pick the right context record from the right run each time you get flow outputs.
Related Content
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Do the following in parallel flow logic
Run actions and subflows in separate paths within an isolated flow logic block.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- Go back to flow logic
Return to a prior step in the flow to repeat a sequence of actions.
- If flow logic
Selectively apply one or more actions only when a list of conditions is met.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Try flow logic
Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.
- Wait for a duration flow logic
Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.