Description:

The Reassign All User Tasks step enables a FlowWright workflow to transfer all active tasks assigned to one user to another user.

Organizations frequently encounter situations where work must be reassigned due to employee leave, role changes, organizational restructuring, vacations, or unexpected absences. Instead of manually reassigning each workflow task, this step automatically transfers all active tasks from the specified source user to the designated destination user.

The step accepts the source and destination users, locates all active tasks assigned to the source user, and reassigns them to the destination user. Once the reassignment is complete, the workflow continues through the configured success path.

Typical uses include:

• Employee leave coverage
• Vacation task reassignment
• Role transition management
• Organizational restructuring
• User account migration
• Temporary workload balancing
• Business continuity planning
• Administrator-driven task reassignment

This step enables organizations to maintain uninterrupted workflow execution while minimizing administrative effort and ensuring that business processes continue without delay.

Usage:

The Reassign All User Tasks step is typically used during administrative workflows, employee offboarding, temporary delegation, workload balancing, or business continuity processes.

During execution:

1. Read the source user name or process user ID.
2. Read the destination user name or process user ID.
3. Locate all active workflow tasks assigned to the source user.
4. Transfer each eligible task to the destination user.
5. Update task ownership within FlowWright.
6. Continue workflow execution through either the True or False return path.

A typical workflow might look like this:

Typical workflow scenarios include:

• Reassigning work before employee vacations
• Handling employee resignation or termination
• Delegating tasks during extended leave
• Balancing workloads across departments
• Supporting organizational restructuring
• Recovering from user account issues
• Maintaining business continuity
• Performing administrative task redistribution

Example:

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

• Create a new process definition named “ReassignAllUserTasksDef” and open it in designer mode. 
• Drag the “ReassignAllUserTasks” step to the canvas.
• Connect the dots between the “Start” and “ReassignAllUserTasks” steps as shown above. 
• Click the "ReassignAllUserTasks" step to configure its "Required" properties. Provide a name for the step. Provide the “From”  and “To” user name or IDs. Click the Save button. Note: Click the "AI Predict" button to have the Copilot 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.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Reassign All User Tasks step, the step transfers active workflow tasks from one user to another.

Tips:

• Verify that both source and destination users exist before executing the step.
• Ensure the destination user has the appropriate permissions to perform the reassigned tasks.
• Execute this step during planned maintenance or administrative workflows whenever possible.
• Notify the destination user after task reassignment to ensure awareness of newly assigned work.
• Route the False execution path to logging and administrator notification activities for easier troubleshooting.
• Combine this step with Send Email, Get Process User Full Name, Get Process Users Full Names, Add Message to History, or reporting steps to provide complete administrative task reassignment workflows.

Notes:

• Both From User Name or ID and To User Name or ID are required properties.
• The step transfers active workflow tasks from one user to another.
• The source and destination users may be specified using either FlowWright user names or process user IDs.
• The step does not modify completed or historical workflow tasks.
• The reassignment affects task ownership but does not alter workflow definitions or process logic.
• Both the True and False execution paths should be implemented for complete workflow handling.
• Appropriate administrative permissions may be required to reassign workflow tasks.

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:

• Source user name or process user ID
• Destination user name or process user ID
• Success and failure workflow branches
• Appropriate administrative permissions

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

Click here to download the sample file.