Asynchronous Flow

Add an Asynchronous Flow step to any flow and use it to call another flow.

Praise Magidi avatar
Written by Praise Magidi
Updated over a week ago

The Asynchronous Flow step is similar to the Synchronous Flow step, but with one main difference in that, it does not wait for the sub-flow to complete.


Using the Asynchronous Flow step

The Asynchronous Flow step calls the sub-flow and then immediately returns to process the remaining steps in your calling flow.

Note:

  • The sub-flow will continue running in the background.

  • As a result, your calling flow may well complete before the sub-flow is finished.

  • Results from the sub-flow are not returned to the calling flow.

The Asynchronous Flow step is located in the Destination drawer in the Steps palette.

  1. Click the Show Steps text button above the flow canvas to display the Steps palette.

  2. Type Async in the search box or scroll down to find the Async Flow step.

  3. Select and drag the Async Flow step to the required location in the flow.


Configuring the Asynchronous Flow

Each Asynchronous Flow step has several settings you can configure to control its operation. When you insert the step, the following dialog box is displayed to edit the relevant control values.


Options

The descriptions below are for each of the setting options:

Flow ID

The Flow ID is the name of the flow that you want to call. You can choose a flow from the dropdown selection list within the same solution or the global solution.

Parameter Mappings

From Path

To Parameter

record.toaddr

toMail

You can map values to the input parameters of the sub-flow.

  • From Path is the path to the source value within the calling flow. You can use any value on the processing object.

  • To Parameter is the name of the input parameter on the flow being called.

Condition Path (Optional)

The path to a value on the processing object that the step can check to ascertain whether the Flow should be executed for the current record. A true value will execute the sub-flow, and a false value will skip the sub-flow.

Source Path

The path to a value on the processing object will be passed to the sub-flow as its data source.

Note: If the sub-flow already has a source step defined, it will be used, and this parameter will be ignored.


Advanced mode options

Select the Gear icon at the top-right of the window to show the advanced options available:

Concurrent Calls

Enter the number of concurrent calls you require the flow to execute concurrently.

Input

  • Record

  • Output

  • Result

  • Original Record


Useful Tutorials

Revisit the Getting Started page for a refresher.

Read more about Steps here.

Did this answer your question?