Description:

The Get Process User Full Name step enables a FlowWright workflow to retrieve the full name of a single user based on the supplied user name or process user ID.

Workflow processes commonly use user names or internal process user IDs to identify workflow initiators, approvers, task owners, reviewers, or assigned users. While these identifiers are appropriate for workflow processing, business users typically prefer seeing readable names in emails, reports, approval summaries, dashboards, and generated documents.

This step resolves a single user identifier into the corresponding full name and stores the result in a workflow variable or global variable. The resolved name can then be referenced throughout the remainder of the workflow.

Typical uses include:

• Displaying the workflow initiator's name
• Showing the current approver's name
• Displaying task owner information
• Personalizing notification emails
• Generating workflow reports
• Populating approval documents
• Creating audit summaries
• Displaying user information on forms

This step enables organizations to present meaningful user information while continuing to use internal user identifiers for workflow processing.

Usage:

The Get Process User Full Name step is typically used before generating reports, displaying user information, creating documents, or sending notifications.

During execution:

1. Read the supplied user name or process user ID.
2. Resolve the identifier to its corresponding full name.
3. Store the resulting full name in the configured workflow variable or global variable.
4. Continue workflow execution through either the True or False return path.

A typical workflow might look like this:

Typical workflow scenarios include:

• Displaying the workflow initiator
• Showing an approver's name
• Personalizing notification emails
• Creating approval documents
• Displaying task ownership
• Generating workflow summaries
• Producing audit reports
• Displaying user information on dashboards

Example:

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

• Create a new process definition named “getUserFullNameDef” and open it in designer mode. 
• Drag a “getUserFullName” step to the canvas. 
• Connect the dots between the “Start” step and “getUserFullName” steps, as shown above. 
• Define a variable or a global to store the result. 
• Click the “getUserFullName” step to configure its “Required” properties. Enter the step name. Enter the workflow user's GUID, separated by semicolons for multiple values. Enter a variable or global reference to store the user's full name. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• The User's GUID is retrieved from the Administration - User Management page. 

• 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 instance, and execute it. Render the process instance. Click the process step. The process step retrieves the workflow user's full name and stores it in the variable or global scope. 

Tips:

• Use this step whenever workflow output is intended for business users instead of system administrators.
• Retrieve the user's full name before generating reports, PDF documents, or email notifications.
• Store the resolved name in a global variable if multiple workflow branches require it.
• Ensure the supplied user name or process user ID is valid before execution.
• Route the False execution path to logging and notification activities for easier troubleshooting.
• Combine this step with Send Email, Generate PDF, Approval History, ProcessInstanceAuditReport, and reporting steps to produce user-friendly workflow output.

Notes:

• The User Name or Process User ID property is required.
• The Variable/Global to Hold the Full Name property is required.
• The step resolves a single user identifier into its corresponding full name.
• The resolved full name is stored in the configured workflow variable or global variable.
• The original user name or process user ID is not modified.
• Both the True and False execution paths should be implemented for complete workflow handling.

Get Process User Full Name vs. Get Process Users Full Names:

Although both workflow steps retrieve user full names from FlowWright, they differ in the number of users they process and the format of the returned results.

As a general guideline:

• Use Get Process User Full Name when a workflow needs the display name of a single user.
• Use Get Process Users Full Names when a workflow needs to resolve and display the names of multiple users in a single operation.

Definition Sample:

You may download the sample workflow definition from the link provided and import it into your FlowWright environment.

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

• User name or process user ID
• Variable/Global to hold the resolved full name
• Success and failure workflow branches

After verifying the configuration, save and publish the workflow before execution.

Click here to download the sample file.