GetUserEmails Step

Use this step to fetch user's email by their User IDs.

Last published at: August 16th, 2025

Description:

This step fetches a list of user email IDs.

 

Inputs

  • userNames - List of semicolon-separated usernames
  • varGlobalEmails - Variable/Global to hold the email list
 

 

Returns

  • True – step executed successfully 
  • False – step failed to execute
 

 

Usage:

 

 

Example:

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

  • Create a new definition called “clsGetUserEmailsDef” and open the definition in designer mode. 
  • Drag a "clsGetUserEmails" step to the canvas.
  • Connect the dots between the “Start” and "clsGetUserEmails" steps, as shown above.
  • Define a variable or a global to store the result.
  • Click the "clsGetUserEmails" step to configure its "Required" properties. Provide a name for the step. 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 "clsGetUserEmails" step to configure its "Optional" properties. Provide a list of user GUID values (retrieved from the User management page) separated by semicolons. Provide the variable or global reference to hold the email list. 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 to view its properties. The step should get the list of user emails and store it in the "variable.emailList" 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.

Click here to download the sample file.