parallelFor - parallelForEnd Step
Description:
The parallelFor step allows you to iterate over multiple steps; the workflow will dynamically expand 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 in the diagram below.
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 process definition called “parallelFor-parallelForEndDef” and open it in Designer mode.
- 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 or a 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. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- A variable reference can also initialize the keys (which 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. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- Once executed, the workflow will automatically expand to have the number of paths based on the number of keys, as shown below.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-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.