- 11 Jan 2023
- 1 Minute to read
- Print
- DarkLight
Branch ForEach Step
- Updated on 11 Jan 2023
- 1 Minute to read
- Print
- DarkLight
Step Details | |
Introduced in Version | --- |
Modified in Version | --- |
Location | Flow Management > Branching |
The Branch ForEach step iterates through every item in an input Collection and passes them to one or more steps. This step is similar to the standard ForEach step, with two key differences:
- It branches the Flow into multiple paths
- The Flows following a Branching ForEach step do not need to complete the loop by forming a return path to the Branching ForEach step. The control of the Flow returns to the Branching ForEach step at the Flow's end automatically.
This can be useful for Parallel Approval processes that involve the iteration and Assignment of multiple pieces of data, i.e., displaying individual retrieved Account data on a Form. The following document demonstrates how to utilize a Branching ForEach step in for such use cases.
Properties
Collection
Property | Description | Data Type |
---|---|---|
Type | Allows a user to select a data type | --- |
Fail If Empty | Creates an outcome path for an empty value | Boolean |
Inputs
Property | Description | Data Type |
---|---|---|
Collection | List of the specified Data Types | List of [DataType] |
Common Errors
Using a Sub Flow between the Branch ForEach and Merge Step is a required configuration. Failure to utilize one will cause the Flow Designer to throw a Validation Warning. Thus, any Form following a Branch ForEach must be run via Sub Flow.
Forum Posts:
Using Branch For Each Step And Getting Errors
Running Branch For Each Step Asynchronously