Description:

This step updates one or more attributes of an existing Active Directory user.

The Update Active Directory User Attributes workflow step connects to Microsoft Active Directory through a configured LDAP connection and updates the selected attributes of an existing user account.

The step identifies the user by the specified username and applies one or more attribute mappings. Each mapping specifies an Active Directory attribute and the value to be written to it. Attribute values can be entered directly or supplied dynamically using FlowWright workflow variables.

The step supports:

• Active Directory user attribute management
• Updating multiple attributes in a single operation
• Configurable LDAP connections
• Attribute-to-variable mapping
• Integration with Microsoft Active Directory

This step can be used for:

• Employee profile updates
• Department transfers
• Organizational changes
• Identity lifecycle management
• HR system synchronization
• User administration
• Business process automation

Usage:

The Update Active Directory User Attributes step is typically placed after an approval or employee information update process within a workflow.

The workflow updates the specified Active Directory user using the configured LDAP connection.

Once the user attributes have been updated, later workflow steps can:

• Synchronize identity systems
• Notify administrators
• Generate audit reports
• Continue identity lifecycle management processes
• Update downstream applications
• Complete employee profile updates

You need to set up an LDAP connection before using this step.

Go to:

Integration → Connections → LDAP Connections

On the Manage LDAP Connections page, click:

Actions → Create

Configure an Active Directory connection before using this workflow step.

Example:

Let’s build and execute the “clsUpdateADUserAttributesDef” example:

• Create a new process definition named “clsUpdateADUserAttributesDef” and open it in designer mode. 
• Drag a “clsUpdateADUserAttributes” step to the canvas.
• Connect the dots between the “Start” and “clsUpdateADUserAttributes” steps.
• Configure a variable or global to store the list.
• Click the "clsUpdateADUserAttributes" step to configure its "Required" properties. Provide a name for the step. Select the LDAP connection from the drop-down list. Provide the “User name”. Click the button to configure attribute mapping. Click the Save button to confirm. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to configure attribute mapping. A pop-up is displayed for configuration. Click the Add Row (+) button to insert an empty row. Provide the user attribute reference and the value. Click the Save button. You can map multiple attributes by using the Add Row function.  

• 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 Process Instance and execute it. When the workflow reaches the Update User Attributes step, FlowWright connects to the configured Active Directory server using the selected LDAP connection and attempts to update the specified attributes for the selected user account. If all attribute updates are successfully completed, the workflow follows the True return path. If the user cannot be found, one or more attributes cannot be updated, or the LDAP connection cannot be established, the workflow follows the False return path. 

• Click the process step to view its properties. The step should update the specified Active Directory user attributes and return True upon successful completion. Use the Read Active Directory User step to verify that the updated attribute values have been applied.

Tips:

• Verify that the LDAP connection has been configured before using this step.
• Use workflow variables to dynamically populate attribute values.
• Verify that the specified user exists before attempting to update attributes.
• Update only the attributes required by the workflow to simplify maintenance.
• Use the attribute mapping editor to efficiently manage multiple attribute updates.
• Use the True and False return paths to implement appropriate success and error handling.
• Combine this step with Read Active Directory User, Enable Active Directory User, or Disable Active Directory User steps to automate identity lifecycle management.

Notes:

• A valid LDAP connection must exist before this step can execute.
• The configured LDAP account must have sufficient permissions to modify Active Directory user objects.
• The specified user account must already exist in Active Directory.
• Only attributes supported by your Active Directory schema can be updated.
• Network connectivity or authentication issues may prevent successful updates.
• The workflow should include appropriate error handling for the False return path.

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: Verify and complete any missing configuration after importing the sample, including:

• LDAP connection
• Username mapping
• Attribute mappings
• Workflow variable mappings
• Active Directory permissions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.