This tab identifies the responsibilities associated with this role. Responsibilities define the workflow actions that will be requested of the role. A role can have any number of responsibilities (including none) associated with it.
Figure 22 - Responsibilities tab
Table 18 Responsibilities tab definition
Title |
Description |
Add Responsibility ID |
To add a responsibility to this role enter the
responsibility ID or search for and select a value using the
Responsibility lookup |
Add |
Click the Add button to add the selected responsibility to this Role document. |
After you add a responsibility to the document, the
system displays additional information about this responsibility.
|
Responsibilities cannot generally be edited via the Role document, but some responsibilities have associated attributes that you must define at the role level. For information about editing responsibilities, see Responsibility. |
Figure 23 - Responsibility details displayed
Table 19 Responsibilities tab definition, continued
Title |
Description |
Responsibility Namespace |
Display-only. The Namespace identifies the application and module associated with this responsibility. |
Responsibility Identifier |
Display-only. The unique system-assigned ID number identifying this responsibility. |
Responsibility Name |
Display-only. The descriptive name of this responsibility. For most Responsibilities the name is 'Review. |
Responsibility Detail Values |
Display-only. This identifies more specific information about the responsibility. Responsibility Detail Values are formatted in a standard way with the following attributes delimited by commas: Route Node: The workflow route level at which this responsibility is invoked. Document Type: The document type for which this responsibility generates workflow requests. Action Details at Role Member Level: A True or False indicator that defines where the details of this workflow action request are defined. If the value is 'True' then action details will be collected when Members are assigned to the role. If the value is 'False' then the action details must be collected when this responsibility is assigned to a role (see Assigning Action Detail Values elsewhere in this section.) Required: Indicates if the routing represented by this responsibility should be required. If this is set to True and the responsibility fails to generate an action request (perhaps because no one is assigned to the associated Role) then the document will go into Exception status. If this routing is optional this value will be False and the document will simply skip this responsibility if no requests are generated. |
Active Indicator |
Display-only. Indicator showing whether this responsibility is active within the system or not. |
Actions |
Click the Delete button to remove this responsibility from this role.
|
Assigning Action Detail Values
When adding a responsibility with an Action Detail Values at Role Member Level value of 'False,' you must complete additional fields in a Responsibility Action sub-section. The system displays this section immediately beneath the responsibility you've just added.
The fields in this sub-section define the type of action requests generated for and the general workflow behavior associated with this responsibility. Entries in these fields cause the system to generate the same type of action requests for all members of this role and handle actions by all members in the same way.
Figure 24 - Responsibility Action details
Table 20 Responsibility Action Subsection definition
Title |
Description |
Name |
Display-only. The namespace and name of the responsibility associated with these action details. |
Action Type Code |
Required. The type of action request that the system is to generate for this responsibility. Options include Approve, FYI and Acknowledge. |
Priority Number |
Optional. If multiple requests are generated at the route node specified on this responsibility, this value determines in the order in which the system will generate these requests. The system processes requests with lower priority numbers before processing requests with higher numbers. Requests with no number are treated as a priority of 1. |
Action Policy Code |
Required. This value determines what happens if multiple members of this role receive the same action request and one of them takes the action. This currently only applies in situations where a single action request is generated to multiple role members (i.e. the action details exist at the role level) or a role is assigned to another role and these nested role members receive an action request. For example, if a role with a responsibility with action details defined at the role level, has three members assigned, all of these members receive the action request defined here; this code determines what the system does when one of them takes action on the document. A value of FIRST indicates that the first role member to take action on the document will automatically clear all the requests for this responsibility that may be in other role member's action lists. A value of ALL indicates that each role member must take individual action to clear his or her requests. |
Force Action |
Check the box to indicate that each user must take this action for this request even if the user has already previously taken action on this document. Leaving the box unchecked allows a request to be immediately fulfilled if the role member has previously taken action on this specific document. |
More: