Description:
The parallelFor step lets you iterate over several steps; the workflow will dynamically grow at runtime based on the keys provided within the step configuration. Steps must be placed between the parallelFor step and the parallelForEnd step, as shown below in the diagram.
Inputs
- varKeys – list of keys comma separated ex: 1,2,3
- varName – name of the variable to hold the key ex: variable.key
Returns
- True – step executed successfully
- False - step failed to execute
The parallelForEnd step lets you define the end marker step.
Inputs
- None
Returns
- None
Usage:
Example:
Let’s build and execute the “parallelFor-parallelForEndDef” example.
- Create a new definition called “parallelFor-parallelForEndDef”
- Select the definition and click the “design” button
- Drag the “parallelFor, parallelForEnd, decision, synchronize, and placeHolder” steps to the canvas
- Connect the dots between the Start and other steps as shown above
- Define a variable/global to store the result
- Click the "parallelFor" step to configure its "Required" properties. Provide a name for the step. Provide a list of comma-separated keys (like 1,2,3 as shown in this example, to iterate the workflow 3 times). Click the Save button.
- A variable reference can also initialize the keys (may contain 7,3,10), and the steps are iterated three times. The keys are always comma-separated by design. For example, a key-value 3 iterates only once and not 3 times.
- Click the "decision" step to configure its "Required" properties. Provide a name for the step. Provide a condition to evaluate. Click the Save button.
- Once executed, the workflow will automatically grow to have the # of paths based on the # of keys as shown below.
Definition Sample:
You may download the sample definition(s) from the link here and later import it (drag-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
NOTE: Please verify and complete the process steps for any missing configurations, such as file path references and database connections after import. Then, save the definition to confirm the changes.