Show/Hide Toolbars

Use the Reassignment page to reassign approval requests from one user to another. When a user is unable to approve for a short period of time, you may want to reassign requests temporarily from the Temporary Reassignment section. If a user is no longer able approve at all, you can assign requests permanently from the Permanent Reassignment section.

Note: If you try to reassign Request A from User 1 to User 2 when both users are required in the same stop, the reassignment does not happen until User 2 has approved the request. When User 2 approves Request A, TeamConnect reassigns the same request from User 1 to User 2, and User 2 must approve again.

Note: Avoid including reassignment entries that create a circular logic and assign the same request back to the original assignee. For example, if you have a reassignment entry that reassigns Request A from User 1 to User 2 and another entry that reassigns Request A from User 2 to User 3, an entry that reassigns Request A from User 3 to User 1 creates a circular logic that does not end until you delete one of the entries.

Conflicting Reassignments

If two reassignment entries conflict, TeamConnect applies the first entry added, which is the first entry in the table.

 

According to the previous image, TeamConnect reassigns all requests to User 5. If you want TeamConnect to reassign invoices until 11/15/2013 to User 6, delete the first entry and enter it again to change the order.

 

According the previous image, TeamConnect reassigns in the following way:

Invoices reassign to User 6 until 11/15/2013.

Invoices reassign to User 5 from 11/16/2013 to 11/22/2013.

All other objects reassign to User 5 until 11/22/2013.

Note: If the entries that conflict are in the two different reassignment tables, you cannot tell which entry you added first from the Reassignment page. Check the Workflow page of a record to determine the first reassignment entry.