Get Organization Structure

Use this step to fetch an user by the organization structure.

Last published at: September 10th, 2025

getOrgUsers Step

Description:

This step fetches an organization user based on the organization's structure.

 

Inputs

  • workflowUserID – id of the user
  • selectOrgUserType – select user type, manager or reporting users
  • varGlobalForID – variable or global to store the user IDs 
 

 

Returns

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

 

 

Usage: 

 

 

Example:

We have included a sample organizational structure below for your reference.

 

Let’s build and execute the GetOrgUsersDef example to fetch the Manager ID of the user (MilanD) and the user's reporting structure to this person.         

  • Create a new process definition named “GetOrgUsersDef” and open it in Designer mode. 
  • Drag the "getOrgUsers, getWorkflowUserID” step to the canvas. 
  • Connect the dots between the “Start” step and other steps, as shown above.
  • Define a variable or a global to store the UserID. 
  • Click the “getWorkflowUserID” step to configure the “Required” properties. Provide a name for the step, the workflow username, and a variable or global to store the userID 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. 

 

  • 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 below. Configure the “Logging” using the following properties. 

 

  • Click the first “getOrgUsers” step to configure the “Required” properties. Set the name to “getOrgUsers (Manager).” Provide the variable or global that contains the workflow userID from the previous step. Select “Managers” as the user type. Provide the variable or global that holds the manager user ID 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. 

 

  • 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 below. Configure the “Logging” using the following properties. 

 

  • Click the second “getOrgUsers” step to configure the “Settings” properties. Enter “getOrgUsers (Report To Me)” as the name. Enter the variable or global that contains the workflow Userid from the previous step. Set the users type to “Reports To Me.” Enter the variable or global that holds the reportee's UserID 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. 

 

  • The “Logging” configuration is necessary for documentation and for measuring workflow progress and the percentage 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 execute it. Render the process instance. Click the process step. The process step should retrieve the user’s “Manager” and the people “ReportingTo” the user, as defined in the FlowWright Organization Structure.  

 

 

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 (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 the import. Then, save the definition to confirm the changes.

Click here to download the sample file.