You may add stop members on the Stops tab of the route. You may add static members and dynamic members to a stop, depending on your needs.
Important: Make sure that there is at least one active user in a route that is being referenced by an approval rule. If no users are identified in a route, the route behaves as if everyone in the route approved the operation. The operation will be completed.
Adding dynamic stop members requires an understanding of Object Navigator. For details, see Using Object Navigator.
Member Types
The Member Type determines how users are included in a route stop as members: as members of a static user group, or as dynamically selected members. The following table explains the three member types.
Stop Member Types in Routes
Member type |
Description |
Example |
Group |
•Allows you to select a specific group to add as a stop member. The request is sent to all active users who are part of the group. •This type of stop member is static. It identifies one group by name. |
The group Senior Claim Officers must approve posting of invoice payments over $100,000. |
User path (Not available in routes that are specified for All objects in the route's General tab.) |
•Allows you to add a stop member based on how they are associated to the object record. For example, a user path could identify the user who created a record, the user who is the main assignee, and so on. •This type of stop member is dynamic. It identifies a user (or, in some cases, multiple users) based on the user's relationship to the record. •A user who is not active does not receive the approval request. |
Posting of invoice payments over $100,000 must be approved by the user who is the main assignee of the claim that is identified in the line item of the invoice. In this example, if more than one project is listed in the line items of the invoice, then the approval goes to the main assignee of each project. |
User with role (Not available in routes that are specified for All objects in the route's General tab.) |
•Allows you to add a stop member based on the user's assignee role in a project. •If a project has more than one assignee with the same role, the approval request is sent to each user who has the selected role. •This type of stop member is dynamic. It identifies a user (or, in some cases, multiple users) based on the user's relationship to the record. •An assignee who is not active does not receive the approval request. •An assignee whose underlying user is inactive does not receive the request. |
Posting of invoice payments over $100,000 must be approved by the user who is the Supervisor of the claim. In this example, if the claim record has more than one supervisor, then the approval goes to each supervisor. |
The steps necessary to add members to a stop are different for each member type. The following are step-by-step instructions to help guide you through adding stop members:
•Adding Groups as Stop Members
