When managing assignments in a workflow step, you can add or move assignments to reflect changes in responsibility—each action follows specific rules to ensure accurate tracking and role alignment.
When you add a new assignment, the system adds an assignment for the selected user on the current step. The existing assignment record is not changed. A new assignment record is added and populated as follows:
Step start date is today’s date.
Due date is recalculated using the new step start date + days allotted.
Name is populated with the selected New assignment from the dialog box.
The remaining fields are populated as already established for assignment records.
The Last updated by and Last update fields are updated. If you select multiple workflows, the new assignment is added for each workflow if the workflow is not closed when the basic rules (below) are adhered to.
A user cannot have more than one assignment on a step. If a selected user already has an assignment, no new assignment will be created. If a selected user is delegating their assignments to a user who already has an assignment, no new assignment will be created for the selected user or the delegate.
All assignments added for the user in the list will have primary assignments created. If they are delegating their assignments, delegate-flagged assignments will be created for their delegates.
When you move an assignment, the system will attempt to replace the assignment record for the user indicated with an assignment record for the newly selected user.
When reassigned, the existing assignment record is marked as closed with the following changes:
Action taken is Reassigned.
Action taken date is today’s date.
The comment for the record is the name of the user reassigned. For example: Jane Doe reassigned.
The remaining columns are unchanged.
A new assignment record is added and populated as follows:
Step start date is today’s date.
Due date is recalculated using the new step start date + days allotted.
Name is populated with the selected New assignment from the dialog box.
The remaining fields are populated as already established for assignment records.
The Last updated by and Last update fields are updated. If you select multiple workflows, the reassignment is done for the selected From user on each workflow for which they have an assignment that is not closed when the basic rules (below) are adhered to.
A user cannot have more than one assignment on a step.
If moving a primary assignment, the new assignment will be primary.
If moving a primary assignment that has an associated delegate-flagged assignment, the new primary assignment will become the primary associated with the delegate-flagged assignment.
If moving a delegate-flagged assignment, the new assignment will be a delegate-flagged assignment associated with the same primary assignment.
A primary assignment can only have one associated delegate-flagged assignment.
If the new assignee is delegating their assignments, an assignment will be made for them and their delegate.
When two responsibilities within a workflow step are reassigned to the same user, that user assumes both roles and receives two distinct assignments. These assignments are not duplicates; each corresponds to a separate responsibility originally assigned to the step.
In workflows configured with Who Must Complete = All, assigning a step to two users (for example, User 1 and User 2) requires each to complete their task independently. If User 1 completes their task and User 2’s responsibility is later reassigned to User 1, PM Compass retains two separate records. These are not duplicates—each record reflects a distinct responsibility initially assigned to User 2, even though both are now under User 1. This ensures that all required approvals are tracked individually, in accordance with the Who Must Complete = All rule.