A User with role stop member identifies a dynamic user who is an assignee of a project. The user who receives the approval depends on which user is identified by the Assignee role indicated in the stop. This stop member type is only available if one specific object is identified for the route in its General tab.
icon and create a path to the necessary project using Object Navigator.When you create a user with role stop member, follow these guidelines:
•If you are creating a user with role stop member and the Assignee role exists within the object for which you are creating the route, you do not need to create a path to identify the role.
•If the role belongs to a different object, you must create a path that indicates which object the role is from, in relation to the object for which you are creating the route, as shown in the examples in the User with Role Examples for Route Stops table.
When creating a path to a user with role, the path must end with an attribute in the object model that identifies a project (custom object). This means that your final selection in Object Navigator must be one of the following:
•project->
•parent->
•applProject->
•leftProject-> (this is not common in routes)
•rightProject-> (this is not common in routes)
•Another attribute that identifies a project.
Important: To build a path that identifies the PROJECT in which the user has the specified assignee role, do not select an end-of-path attribute that identifies the user.
The following table provides sample User with role paths for stop members.
User with Role Examples for Route Stops
Project identified by this path |
Example |
What to select in Object Navigator to build this path |
The parent project of the current project. Note: This path may only be used for custom objects that have parent-child relationships. |
When creating a route for Claim (a custom object): If Policy is the parent object of Claim, this would send the approval request to assignees of the policy record that is the parent of the claim record. |
parent->(ok) |
The project to which the current object (such as Task or Expense) is related. |
When creating a route for Task, Expense, or other system object that may be related to a project record: This would send the approval request to assignees of the project that is selected in the General information for the record. |
project->(ok) |
The project to which an account belongs. |
When creating a route for account: This would send the approval request to assignees of the project that is selected in the General information for the account. |
applProject->(ok) |
The project referenced on a line item of an Invoice. If more than one project is listed, then the approval goes to each user who has the selected role in each of the projects. |
When creating a route for invoice: This would send the approval request to assignees of the projects that are referenced by each line item on the invoice. If all line items in the invoice reference the same project record, then only the assignees of that project receive the approval request. |
lineItemList-> (traverse) project->(ok) |
The parent of the parent project of the current project. |
When creating a route for litigation (a custom object): In a litigation record that has a parent claim, which in turn has a parent policy, this would send the approval request to the assignees of the policy record. |
parent->(traverse) parent->(ok) |
When adding a user with role as a member of a stop, keep in mind that if there is no user identified by the path, or if the user is inactive, then the member is not added to the stop. For example, if you want the route to go to the General Counsel assignee of a project and this is the only member of the stop, then the stop is skipped if there is no such assignee, and the route automatically proceeds to the next stop. If there are no further stops, then the request is approved.
Tip: You may add all project assignees as members of a stop by adding a User with role member for each role that is possible for the project. TeamConnect automatically routes the approval request to all users who are assignees of the project.
