> 
> 
> 
The Responsibility document allows you to create new responsibilities or edit existing ones. The Responsibility Lookup allows you to search for and view existing responsibilities. You can view summarized information about the responsibility detail values as well as the roles with which the responsibility is currently associated.
Only members of OLE-SYS Technical Administrator or OLE-SYS Manager role can create or modify a Responsibility document and it does not route for approval. Information about the Responsibility document follows detailed information about the Responsibility Lookup below.
Note
Caution should be exercised when modifying existing responsibilities or adding new ones. Relatively minor changes can result in disruptions to the workflow of documents if made in error. Changes should be made only after sufficient testing with your local configuration.
Responsibility Lookup search criteria
|
Title |
Description |
|
Template Namespace |
Optional. To search for a responsibility based on its template namespace (that is, the name of the application and module to which its responsibility template belongs), select the appropriate namespace. |
|
Template Name |
Optional. To search for a responsibility based on the name of the template it is based on, enter the appropriate template name. |
|
Responsibility Namespace |
Optional. To search for a responsibility based on its namespace, select the appropriate responsibility namespace. |
|
Responsibility Name |
Optional. To search for a responsibility by name, enter its name. |
|
Role Namespace |
To search for a responsibility based on the namespace of the role to which it is assigned, enter the appropriate role namespace. |
|
Role Name |
Optional. To search for a responsibility based on the role to which it is assigned, enter the appropriate role name. |
|
Principal Name |
Optional. To search for a responsibility based on the principals that currently have this responsibility through their association with a role, enter an appropriate principal name. |
|
Group Namespace |
Optional. To search for a responsibility based on the namespace of groups that have this responsibility through the group's association with a role, enter an appropriate group namespace. |
|
Group Name |
Optional. To search for a responsibility based on the name of a group that has this responsibility through its association with a role, enter an appropriate group name. |
|
Attribute Value |
Optional. A specific responsibility detail value associated with a responsibility. |
 |
The Responsibility results display contains the fields described in the table below.
Responsibility Lookup results fields
|
Title |
Description |
|
Actions |
Actions allow selection of edit or copy for each responsibility displayed. |
|
Template Namespace |
The code identifying the application and module the template pertains to. Because responsibilities pertain to workflow, most responsibility templates are associated with the KR-WKFLW (Kuali Rice-Workflow) namespace. |
|
Template Name |
The template the responsibility is based on. A template usually defines, in a broad sense, what the responsibility is. Since responsibilities normally are normally associated with action requests for user review, most responsibilities have a template name of 'Review. |
|
Responsibility Namespace |
The code designating the application and module this responsibility is associated with. This code usually corresponds to the namespace of the document type for which the responsibility generates action requests. |
|
Responsibility Name |
The name of this responsibility. In most cases the responsibility name will be the same as the associated template name ('Review'). Like permission names, responsibility names are not unique. Most OLE responsibilities have a name of 'Review. |
|
Responsibility Detail Values |
Display only. Detailed information that defines what document this responsibility generates action requests for, when the requests are generated and how they are handled by workflow. Unlike permissions, which sometimes have different detail values, responsibility detail values generally contain the elements defined below. routeNodeName: The point in a document's workflow routing at which this responsibility generates requests. documentTypeName: The name of the document type for which this responsibility generates action requests. This value may also be a parent document type, which indicates that this responsibility applies to all child documents that contain the appropriate route node. actionDetailsAtRoleMemberLevel: A True or False indicator that defines where the system collects details of this workflow action request. If the value is 'True,' the system collects action details when members are assigned to the role. If the value is 'False,' the system collects action details when this responsibility is assigned to a role. required: A True or False value that indicates whether the system is required to generate an action request for this document type. If the value is 'True' and the document generates no requests associated with this responsibility, then the document will go into exception status. If the value is 'False' and the responsibility generates no action requests, then the document continues to route as normal. |
|
Granted to Roles |
Lists the namespace and name of roles that have this responsibility. Click on the linked name to view the Role Inquiry. |
To view an Inquiry screen for a responsibility, select the Responsibility Name of the appropriate row in the search results. The Inquiry contains the same information displayed in the search results in a slightly different format.
 |
The Responsibility document includes Document Overview, Responsibility Info, and Responsibility Details tabs.
 |
This tab identifies the responsibility with a unique system-assigned ID number, a namespace, name and description.
 |
Responsibility Info tab definition
|
Title |
Description |
|
Responsibility Identifier |
Display only. The unique, system-assigned ID number that identifies this responsibility. |
|
Responsibility Namespace |
Required. An indicator that associates the responsibility with a particular application and module. |
|
Responsibility Name |
Required (defaults to 'Review'). A text name identifying this responsibility. Note that this is the only valid value for this document. You cannot use the Responsibility document to establish or modify Responsibilities with the name 'Resolve Exception' -these require a technical resource to modify. |
|
Responsibility Description |
Optional. Enter a text description of what this responsibility does. |
|
Active Indicator |
Required (defaults to 'Yes'). Change the default selection if you wish this responsibility to be inactive. Inactive responsibilities will be disregarded by Workflow. |
This tab identifies the document type and route node associated with this responsibility. It also defines other responsibility information such as whether or not the action details reside at the role member level.
 |
Responsibility Details tab definition
|
Title |
Description |
|
Document Type Name |
Required. Enter the name of the
document type this responsibility is associated with or use
the Document Type Lookup
|
|
Route Node Name |
Required. The name of the route node at which this responsibility should be invoked. |
|
Action Details at Role Member Level |
Required (defaults to False). Check this box if you want role members associated with this responsibility to be able to define the type of workflow action they will need to take in order to fulfill the action request it generates. |
|
Required |
Required (defaults to False). Check this box if you wish documents of this type to go into Exception status if this responsibility does not generate at least one action request. |
|
Qualifier Resolver Provided Identifier |
Optional. In most cases this field should be blank. It can be used as an additional identifier KIM will use to choose the correct responsibility information for a given doc type. The document type must pass the provided identifier to KIM. This is only used in OLE based data for the routing of group documents. The group type ID is populated here and determines how the document routes (Chart and Organization type groups do organization review routing and default group types do not). |
