Description:

The List of User Workflow IDs workflow step retrieves a list of user process IDs based on a supplied list of user names.

The users are specified as a semicolon-separated list of user names. The resulting user ID list can optionally be stored in a FlowWright Variable or Global variable for use by subsequent workflow activities.

The step supports:

• Specifying multiple user names.
• Separating multiple user names with semicolons.
• Retrieving the process IDs associated with the specified users.
• Storing the resulting user ID list in a Variable or Global variable.
• Using workflow-generated user information as input.
• Routing the workflow through True or False return paths.

Usage:

The List of User Workflow IDs step is typically used when a workflow needs to obtain the process IDs associated with one or more FlowWright users during process execution.

The workflow can supply a semicolon-separated list of user names and optionally specify a Variable or Global variable to hold the resulting user ID list.

A typical workflow pattern is:

Identify Users → List of User Workflow IDs → Store User ID List → Continue Process

For example:

Get User Names → List of User Workflow IDs → Process User IDs → Continue Workflow

The Variable/Global to hold the user ID list property provides a destination for the resulting list.

The step is useful when the user names are available, but subsequent workflow processing requires their associated process IDs.

Typical Workflow Suggestions:

Retrieve Process IDs for Multiple Users

Use the step when a workflow needs to retrieve process IDs for several users.

Example:

Identify Users → List of User Workflow IDs → Process User IDs → Continue Workflow

Provide the user names as a semicolon-separated list and store the resulting IDs in a Variable.

Retrieve User Process IDs from Dynamic Workflow Data

Use this step when the list of users is determined during workflow execution.

Example:

Determine Users → List of User Workflow IDs → Process User IDs → Continue Process

The user list can be populated dynamically from workflow data.

Retrieve IDs Before User-Specific Processing

Use this step when subsequent workflow activities require user IDs rather than user names.

Example:

Receive User Information → List of User Workflow IDs → Process Retrieved IDs → Complete

The retrieved user ID list can be stored in a Variable or Global variable.

Build a User ID List for Subsequent Workflow Processing

Use this step when multiple user names need to be converted into a user ID list before another workflow activity executes.

Example:

Collect User Names → List of User Workflow IDs → Prepare User ID Data → Subsequent Activity

The output Variable can be used by the subsequent activity.

Retrieve User IDs Before a Workflow Decision

Use this step when retrieved user IDs are required before evaluating subsequent workflow logic.

Example:

Identify Users → List of User Workflow IDs → Evaluate Workflow Condition → Branch Workflow

The resulting user ID list can be used as input to subsequent workflow processing.

Example:

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

• Create a new process definition named “clsGetUserWorkflowIDsDef” and open it in designer mode. 
• Drag a "clsGetUserWorkflowIDs" step to the canvas.
• Connect the dots between the “Start” and "clsGetUserWorkflowIDs" steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Define a variable or a global to store the result after execution.
• Click the "clsGetUserWorkflowIDs" step to configure its "Required" properties. Provide a name for the step, the external user name, and a variable or global reference to store the user's GUID value. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the "clsGetUserWorkflowIDs" step to configure its "Optional" properties. Enter user names separated by semicolons. Provide the variable or global reference to store the user's GUID value.

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

• Save the process definition and create a new process instance. When the workflow reaches List of User Workflow IDs, FlowWright processes the supplied user names and retrieves the associated user process IDs. If an output Variable or Global variable has been configured, the resulting user ID list is stored there for use by subsequent workflow activities. The workflow then follows the appropriate True or False return path.

Tips:

• Use semicolons to separate multiple user names.
• Verify that the supplied user names identify the intended FlowWright users.
• Use a workflow Variable when the list of users is determined dynamically.
• Use a meaningful Variable or Global variable name for the resulting user ID list.
• Verify the resulting user ID list before passing it to downstream processing when user identification is important.
• Use the True path for normal processing after successful ID retrieval.
• Use the False path for appropriate error handling or alternate processing.
• Test the step with both individual and multiple-user inputs.
• Test the semicolon-separated format when multiple users are required.
• Avoid hard-coding user lists when the workflow can determine users dynamically.
• Validate user names before executing the step when the input originates from external or user-provided data.
• Test both True and False workflow paths before deploying the process.
• Document the expected format of the user-name list when the step is used as part of a larger workflow.

Definition Sample:

You may create a FlowWright process definition containing the List of User Workflow IDs step and configure it according to the requirements of the workflow.

When configuring the step, verify:

• List of user names.
• Semicolon separation when multiple users are supplied.
• Variable or Global variable used to hold the user ID list.
• Workflow Variable references when the user list is dynamic.
• True workflow path.
• False workflow path.
• Environment-specific workflow configuration.

After verifying the configuration, save the process definition before executing a process instance.

Click here to download the sample file.