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.
The parallelFor step lets you define the start marker step.
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, Synchronize, Placeholder and Decision steps” to the designer canvas
- Connect the Start step and other steps as seen above
- Define a variable/global to store the key value
- Click the "parallelFor" step to configure its "Required" properties. Provide a name to the step. Provide a list of key values as below. The keys are comma-separated (like 1,2,3 in this example), and the steps are iterated 3 times. A variable reference can also initialize the keys (may contain 7,3,10), and the steps are iterated 3 times. The keys are always comma-separated by design. E.g., key-value 3 iterates only once and not 3 times. Provide the variable/global reference to hold the key value. Click the Save button.
- Click the "decision" step to configure its "Required" properties. Provide a name to the step. Provide the condition to evaluate. Click the Save button.
- Click the "parallelForEnd" step to configure its "Required" properties. Provide a name to the step. Click the Save button.
- Save the process definition, create a new instance, and execute. Render the process instance. Once executed, the workflow will automatically grow to have the number of paths based on the number of keys, as shown below.
Definition Sample:
You may download the ZIP file and extract 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.