Stops represent approval rule check points. The route follows the order in which you organize the stops, starting with Stop 1. A stop consists of members who may approve or reject the operation attempted by a user. All members of each stop receive the approval notice in their My Approvals screen.
Points To Remember
•If all users in a stop do not exist, the stop is skipped and the route proceeds to the next stop. For example:
oIf a stop includes only the Main Assignee of a Claim and there is no Main Assignee, then the stop is skipped and the route proceeds to the next stop.
oIf a stop includes only a certain assignee in the parent project of a project that is being deleted. If there is no parent project, then the route proceeds to the next stop.
oIf a user with a specified role is assigned to a stop in a route, and there is no such role assigned to any active assignee or group, the assignee is skipped and the request goes to the next approver.
•If an assigned user with a specified role exists, but the user account is inactive, an error message appears if all members are required for approval or if there are no other valid members in the stop.
•Rejection of an approval request always works on a "first come, first serve" basis. Once any designated approver rejects a request, the request record is removed from the My Approvals list of all route members, regardless of which stop in the route the rejection occurred.
•Approval may work on a "first come, first serve" basis only if you want it to. For each stop of the route, you may control whether one approval is enough to allow the operation, or all stop members must approve the operation before the route proceeds to the next stop.
•If the sequence of approval does not matter, then you must place all of these members in one stop. Placing multiple members in one stop and requiring approval from all stop members (selecting the check-box) allows you to give more time for all members to approve the operation, rather than having them wait for the previous stop members to approve the operation first.
•If the sequence of approval does matter, then each member whose approval is required must be placed in a separate stop, in the order in which their approval is required. You must also make sure that the expiration time allows for all stops to be reached.
Stops may be viewed, added, deleted, or modified on the Stops tab of the route. The Stops tab also defines the order of the stops and whether all members of each stop must approve the request before the route proceeds to the next stop.
Stops Tab
The following table describes the items on the Stops tab.
Field or button
|
Description
|
new
|
Click to create a new stop for the route. The new stop is added to the end of the route.
|
All members of this stop are required for approval
|
Select this check-box if all members of the stop are required to approve the request. If the check-box is selected, then the route does not continue to the next stop until all users in the stop have approved the operation.
If this check-box is NOT selected, then the route continues to the next stop as soon as one user in the stop has approved the operation.
This check-box requires all members no matter how they are added to the stop. This means that a member's approval is required in all of the following situations:
•More than one member (of any type) is added to the stop. Each member's approval is required. •A Group is a member of the stop. This check-box requires an approval from all members of the group. •A User with role or User path stop member points to more than one user with the specified role. For example, there are two General Counsel assignees (user with role). Approval is required from each assignee with the specified role. Whether or not this option is selected, a single user may reject the attempted operation and thus delete the request from the My Approvals screen of all route members. You cannot set a route to reject an operation only after all members have rejected it.
|
Member Type
|
Select the type of stop member you want to add to the stop. For details, see Adding Stop Members.
|
Member
|
Select or identify the user or group you want to add to the stop. For details, see the following:
•Adding Groups as Stop Members •Adding User Paths as Stop Members •Adding Users With Roles as Stop Members |
Member List
|
Displays the members of the corresponding stop.
|
Move Up or Down Arrows
|
Use these arrows to change the order of the stops if needed. Click the respective arrow to move the entire stop up or down one level.
The route follows the order in which you organize the stops, starting with Stop 1.
|
delete
|
Click to delete the corresponding stop from the route. Each delete button corresponds to the stop with which it is aligned.
Note: Do not confuse the delete buttons for the stops with the delete button at the bottom of the screen that appears in all batch screens. The delete button for the batch screen applies to stop members rather than an entire stop.
|
Visit stops in sequence
|
Select to specify that the route visits each stop in numerical order.
This option does not appear if you can use the route with all record types.
|
Custom sequence
|
Select to place a condition on a stop to determine whether the route visits the stop. Refer to the Custom Sequence Entries table for details about this field.
This option does not appear if you can use the route with all record types.
|
|
