A User path stop member identifies a dynamic user. The user who receives the approval depends on which user is identified by the path. This stop member type is only available if a specific object is identified for the route on its General tab.
When adding a user path as a member of a stop, keep in mind that if there is no user identified by the path, then the member is not added to the stop. For example, if you want the route to go to the Main Assignee of a project and this is the only member of the stop, then the stop is skipped if there is no Main Assignee, and the route automatically proceeds to the next stop.
When creating a path to a user for a member of a stop, the path must end with an attribute in the object model that identifies a user. This means that your final selection in Object Navigator must be one of the following:
•user->
•createdBy->
•modifiedBy->
•expensedBy->
•enteredBy->
•transitionedBy->
•Another attribute that identifies a user.
Important: Only users may be members of a route. Do not select an attribute that identifies a contact as your final selection for a user path.
The following table provides sample user paths created for a stop member.
User Path Examples for Route Stops
User identified by this path |
What to select in Object Navigator to build this path |
The user who created the record. |
createdBy->(ok) |
The user who is the Main Assignee of the project for which you are creating a route. |
mainAssignee->(traverse) user->(ok) |
The user who is the Main Assignee of the project to which the current object for which you are creating a route (such as Account, Expense, Task, etc.) is a related object. |
project->(traverse) mainAssignee->(traverse) user->(ok) |
The user who is the main assignee of the project indicated in the invoice's line items (for a route created for the Invoice object). |
lineItemList->(traverse) project->(traverse) mainAssignee->(traverse) user->(ok) |
The user who entered or posted the expense (for a route created for the Expense object). |
expensedBy->(ok) |