In the following cases, the company administrator is a user who has permissions to reassign the tasks.
Case 1: Selected new assignee is a CC user
- Business Process record R1 currently has been assigned to user A and has been CC'd to user B
- User A has been inactivated
- Company Administrator has now reassigned this task to user B
- User B will receive the task reassignment notification in addition to seeing the task in the Tasks log.
- In addition to this, the notification for this task which the User B had received because of being a CC'd user, will be removed from the Notifications log.
Case 2: Selected new assignee is not in the Workflow (WF) setup
In the event that the selected assignee is not in the WF setup, the user will still get the reassigned task. This means that the task will be seen in the Tasks log.
Note: By means of Tasks reassignment, the system will not add the user to the Workflow setup. This action has to be performed by the administrator who is setting up the workflow setup. Similarly the user will not have navigation level permissions to the Business Process log that the task belongs to. This action again has to be performed by the administrator.
Case 3: Selected new assignee had previously declined the task
If the selected new assignee had previously declined the task, then post reassignment, the task will be seen in the Tasks log.
Assumption: The workflow setup allows declining of the task.
Case 4: Single Completion policy - Non participating assignee has been inactivated
A non participating assignee is one who has not acted on a task. When such a user is inactivated, the in-flight records which had this user in one of the steps will not be seen in the Tasks reassignment log.
Case 5: Completion Policy - All Consensus
- Business Process record R1 currently has been assigned to users A, B and C
- User A accepts the Task routes the record to step A
- User B declines the task
- User C has been inactivated
- Company Administrator reassigns the Task of User C from the Tasks Reassignment log to user D
- User D accepts the Task and routes the record to step B
- The record will get routed to the resolving action since the users have taken different actions
Case 6: Completion Policy - All Majority
- Business Process record R1, currently has been assigned to users A, B and C
- User A accepts the Task and routes the record to step A
- User B accepts the Task and routes the record to step B
- User C has been inactivated
- Company Administrator reassigns the Task of User C to user D
- User D accepts the task and routes the record to step B
- The record will get routed to Step B since the majority of the users took the action of routing it to Step B