Home Paris Now Platform Capabilities Now Platform capabilities Flow Designer Flows Flow logic Dynamic flows

Dynamic flows

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.

To use Dynamic Flow, the flow designer does the following:

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 of the flow or subflow that you want to run. Generate a flow or subflow name dynamically by entering a string and concatenating it with data pill values. Note: 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.

Note: You see more inherited inputs after you select a Flow Template.

Get flow outputs

Dynamic Flow outputs appear in the data pane as Record type data pills that are named as Context. You can use these flow contexts to derive the runtime values for dynamic flow outputs with the Get Flow Outputs flow logic. To use Get Flow Outputs, the flow designer does the following:

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 Dynamic Flow > Context.

For more information on using Get Flow Outputs, see Getting started with Dynamic Flow and Get Flow Outputs.

Design considerations

Consider using 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: If the inputs of the dynamic flow don't match the inputs of the flow template, the system throws an error and the main flow can't run properly.
Use the correct context when getting flow outputs: If you are using Dynamic Flow more than once within a flow, make sure to drop in the correct context data pill from Get Flow Outputs.

Previous topic

Next topic

Release version

Dynamic flows

Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.

To use Dynamic Flow, the flow designer does the following:

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

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 of the flow or subflow that you want to run. Generate a flow or subflow name dynamically by entering a string and concatenating it with data pill values. Note: 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.

Note: You see more inherited inputs after you select a Flow Template.

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 Dynamic Flow > Context.

For more information on using Get Flow Outputs, see Getting started with Dynamic Flow and Get Flow Outputs.

Design considerations

Consider using 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: If the inputs of the dynamic flow don't match the inputs of the flow template, the system throws an error and the main flow can't run properly.
Use the correct context when getting flow outputs: If you are using Dynamic Flow more than once within a flow, make sure to drop in the correct context data pill from Get Flow Outputs.

How search works:

Topics are ranked in search results by how closely they match your search terms

Dynamic flows

Dynamic flows

Dynamic flow templates

Inputs

Get flow outputs

Design considerations

On this page

Dynamic flows

Dynamic flows

Dynamic flow templates

Inputs

Get flow outputs

Design considerations

Log in to personalize your search results and subscribe to topics