Responsibility

You are here: System Administration > Identity > Identity

Responsibility

Maint. doc. Label: Review Responsibility

The Responsibility administration maintenance 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.

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. Typically, the Responsibility document does not route for approval and is only used by members of the System Manager or Technical Administrator roles to create new or modify existing records.

Document Layout

Figure 1167 Responsibility Administration Maintenance Document Example Layout

Responsibility Info Section

The Responsibility Info section of the Responsibility administration maintenance document is a unique section that allows you to specify and maintain the details associated with the reference table record in fields. It identifies the responsibility with a unique system-assigned ID number, a namespace, name and description.

Figure 1168 Responsibility Administration Maintenance Document – Responsibility Info Section Example

Table 812 Responsibility Administration Maintenance Document – Responsibility Info Section Field Descriptions

Field	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. Use the drop-down menu by clicking the down arrow to display the list, and then click on an item in the list to highlight and select it to populate the box with your selection.
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. Click within the checkbox to select the item. A check mark appears within the checkbox to indicate the item is selected. Click within the checkbox again to clear the mark and deselect the item.

Responsibility Details Section

The Responsibility Details section of the Responsibility administration maintenance document is a unique section that allows you to specify and maintain the details associated with the reference table record in fields. It 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.

Figure 1169 Responsibility Administration Maintenance Document > Responsibility Details Section Example

Table 813 Responsibility Administration Maintenance Document > Responsibility Details Section Field Descriptions

Field	Description
Document Type Name	Required. Enter the name of the document type this responsibility is associated with. Click the lookup icon to search for and return the value to populate the box automatically, or if known, type the value in the box.
Route Node Name	Required. The name of the route node at which this responsibility should be invoked.
Action Details At Role Member Level	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. (defaults to No)
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. Click within the checkbox to select the item. A check mark appears within the checkbox to indicate the item is selected. Click within the checkbox again to clear the mark and deselect the item.
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 KC base data for the routing of group documents. The group type ID is populated here and determines how the document routes.

Examples

Figure 1170 Responsibility Administration Maintenance Document Example Values

Common Features

This maintenance document includes the following features that are common to most KC maintenance documents:

Table 814 Links to Common Maintenance Document Component Instructions

Common Maintenance E-Doc Component	Cross-Reference Links To Usage Instructions
Document Header	For more information, see “Header Area” on page 99 in E-Doc Fundamentals.
Document Overview Section	For more information, see “Document Overview” on page 103 in Common E-Doc Tabbed Sections.
Notes and Attachments Section	For more information, see “Notes and Attachments” on page 104 in Common E-Doc Tabbed Sections.
Ad Hoc Recipients Section	For more information, see “Ad Hoc Recipients” on page 106 in Common E-Doc Tabbed Sections.
Route Log Section	For more information, see “Route Log” on page 107 in Common E-Doc Tabbed Sections.
Action Buttons	For more information, see “Action Buttons” on page 81 in Selection, Entry and Action Tools.

Process

For information about searching for, initiating, editing, copying, submitting, saving, closing, canceling, and/or routing a maintenance document, see “Common Maintenance E-Doc Operations” on page 129 in the Overview section.