getUsersForRole Step
Description:
This step fetches all users assigned to the application role and stores their GUID values in a variable.
Inputs
- roleID – selected role
- variableToStoreValue – Variable to store the value
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “GetUsersForRoleDef” example.
- Create a new process definition called “GetUsersForRoleDef” and open the definition in designer mode.
- Drag a “getUsersForRole” step to the canvas.
- Connect the dots between the “Start” step and “getUsersForRole” steps, as shown above.
- Define a variable or global to store the user's list of GUID values.
- Click the "getUsersForRole" step to configure its "Settings" properties. Provide a name for the step. Click the button to select the application roles. Provide a variable or global reference to store the user list GUID values after execution. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- Click the button to select the application roles. A pop-up window shall be displayed for configuration. Use the navigation keys to select the application roles. Click the Save button.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the 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 instance, and then execute it. Render the process instance. Click the process step. The step should retrieve the user's GUID values for the selected roles and store them in a variable or global, as configured.
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.