This tab details the route nodes on each document and additional information about the "responsibility" or the action requested at each route node.
Indicates whether or not an approval is required at this route node. If Yes and a role is not assigned, then the document will route to exception. If No, then it will route to this node only if a role is assigned.
Action Details at Role Member Level
When adding an assignee to a role if the Action Details at Role Member Level = Yes, then you have to set the action details qualifiers, action requested, etc. for each assignee.
When set to No, the assignees (role members) inherit the action details set for the responsibility.
For example, role 39 has a responsibility where Action Details.. = N; so when you add an assignee - that's it. Role 28 on the other hand, responsibility Action Details = Y, so when adding an assignee, you have to also indicate what action they need to take.
Role 39 - Action Details at the Role Member Level = No
Role 39 Responsibilities - the Responsibility Action section is complete
Role 39 Members - do not have their own Responsibility Actions
Role 28 - Action Details at the Role Member Level = Yes
Role 28 Responsibilities - No Action Responsibility section
Role 28 Members - Responsibility Actions are completed for each Role Member
Granted to Roles
The roles to which the responsibility at this route node are assigned.
Indicates the document from which the responsibility is inherited. If you wanted to skip a particular route node, you can copy the responsibility and create it for the specific document you want to skip. Do not assign it and make sure the Required flag= No.
Opens the Responsibility document for editing.