Description:

This step iterates through a list of items.

The Loop Each workflow step accepts a delimited list of values, separates the list into individual items using the specified delimiter, and executes the connected workflow path once for each item.

During each iteration, the current item is stored in a FlowWright Variable or Global Variable, allowing downstream workflow steps to process the value independently. After all items have been processed, the workflow continues through the Loop Completed path.

This step provides an efficient way to automate repetitive processing without requiring duplicate workflow logic.

The step supports:

• Iterating through delimited lists
• Configurable item delimiters
• Processing one item at a time
• Storing the current item in a Variable or Global Variable
• Separate workflow paths for loop execution and loop completion
• Integration with FlowWright workflow automation

This step can be used for:

• Batch processing
• File processing
• Email distribution
• User provisioning
• Document automation
• API integrations
• Business process automation

Usage:

The Loop: Each step is typically placed before workflow activities that must be repeated for each value in a list.

The workflow splits the supplied list using the configured delimiter, stores the current value at each iteration, executes the connected workflow path, and automatically advances to the next item until the list has been fully processed.

After the final item has been processed, the workflow continues along the Loop Completed path.

A typical workflow might look like this:

During each iteration, later workflow steps can:

• Process documents
• Send emails
• Call REST APIs
• Update databases
• Create users
• Archive files
• Execute business rules

After all items have been processed, the workflow can generate reports, send notifications, or continue with additional workflow activities.

Example:

Let’s build and execute the “loopEachStepDef” example.          

• Create a new process definition called “loopEachStepDef” and open it in Designer mode.
• Drag a “placeholder, loopEachStep” step 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 "loopEachStep" step to configure its "Required" properties. Provide a name for the step. Provide a list of items to iterate over. Specify the delimiter character used to separate the items (for example, a comma). Provide the variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Loop Each step, FlowWright separates the supplied list using the configured delimiter, stores each item in the configured Variable or Global Variable, and executes the Loop path once for every item. After the final item has been processed, FlowWright automatically follows the Loop Completed return path. Click the process step to view its properties. The step should iterate through every list item, populate the configured Variable or Global Variable on each iteration, and continue along the Loop Completed path after processing all items.

Tips:

• Use workflow variables to dynamically build the list before entering the loop.
• Ensure the delimiter matches the format of the supplied list.
• Store the current item in a Global Variable when multiple workflow steps within the loop require access to it.
• Keep the workflow connected to the Loop path focused on processing a single item.
• Place summary generation, notifications, or cleanup activities on the Loop Completed path.
• Use this step together with document processing, DMS operations, REST calls, or user management steps to automate batch operations.
• Avoid modifying the original list during iteration.
• Combine this step with JSONPathToList, Get Documents, Send Email, REST Call, Create Users, Archive Document, or Azure OpenAI Chat Completion workflow steps to build scalable batch-processing workflows.

Notes:

• The supplied list is separated using the configured delimiter.
• Each iteration stores a single item in the configured Variable or Global Variable.
• The Loop return path executes once for every item in the list.
• The Loop Completed return path executes only once after the final item has been processed.
• Empty list values or incorrect delimiters may result in fewer iterations than expected.
• This step controls workflow iteration only and does not modify the supplied list.
• The workflow should include appropriate handling for both the Loop and Loop Completed return paths.
• This step is particularly useful for processing collections of files, users, email addresses, document IDs, API requests, or any other delimited list of values.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition page.

Note: Verify and complete any missing configuration after importing the sample, including:

• List of items
• Delimiter
• Variable or Global Variable mapping
• Workflow connections for both Loop and Loop Completed
• Workflow variable definitions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.