> 
> 
> 
This special view combines KIM data with OLE Document Type Hierarchy. It visually displays the parent and child relationships between OLE document types and the route nodes that are associated with each. Users may also choose to view detailed configuration for each document type, including all KIM permissions and responsibilities related to that document.
Users who are authorized to edit document types, permissions and responsibilities may access these options directly via this screen.
When you access the Routing & Identity Management Document Type Hierarchy screen, the system initially displays the document hierarchy itself. Document types are indented under their parent document types.
 |
To display the Document Type Inquiry for a document, click the document type name.
Users with permissions to edit document types will see an extra link displayed for each type. To initiate an OLE Document Type Maintenance document to edit a document type, click the Edit Document Type link for it.
If a given document type does workflow routing, then the system displays the route nodes associated with this type directly below the name of the document. Route nodes are listed in the order in which this document passes through them. Document types with branching routing logic may have further indentation displaying route nodes that a document may only pass through under certain conditions.
To open a separate window displaying additional information about a document type, click the View Document Configuration link.
 |
This view includes Document Information, Permissions and Workflow / Responsibilities tabs.
This tab provides basic information about the document type. Much of the information here is identical to that available in the Document Type Inquiry.
 |
Document Information tab definition
|
Title |
Description |
|
Name |
The name that uniquely identifies this type of document. If the user viewing the Configuration screen has permission to edit document type maintenance documents, the system also displays the Edit Document Type link. |
|
Label |
A longer, more descriptive name for this type of document. In some cases the name and the label may be identical. |
|
Parent Name |
The type of document that is the parent to (i.e., higher than) this document type in the document type hierarchy. To display the Document Configuration view for the parent document type, click the linked parent name. |
|
Doc Handler URL |
The URL for the document handler associated with this document type. This information is helpful for technical users. |
|
Help URL |
The URL for the online help associated with this document type. |
|
Child Document Types |
If this document type is a parent, the system displays all of its types for all of its children document types. To see the document configuration view for a child document type, click the link for the desired child document type. |
This tab identifies the KIM permissions that are invoked by this type of document. Collapsible sections indicate how the document type is associated with each permission.
The Defined for This Document section lists permissions that specifically refer to this document type. But many document types receive most, if not all, their associated permissions by inheriting them from parent document types. Additional tabs display this inherited information and the name of the document type from which the permissions are inherited. For example, in the screenshot below, this document type inherits permissions from both OLEChartComplexMaintenanceDocument and OpenLibraryEnvironmentComplexMaintenanceDocument.
 |
Because more specific permissions override more general ones, some listed permissions may not apply. The system displays overridden permissions as gray strike-through text. In the example below the 'Initiate Document' permission inherited from OLE is overridden by a more specific permission displayed in Inherited From: OLEChartComplexMaintenanceDocument section.
 |
Permissions tab definition
|
Title |
Description |
|
Template Name |
Display only. The name of the permissions template on which this permission is based. The template often defines, in a broad sense, what the permission controls. Similar types of permissions have the same template. |
|
Permission Name |
Display only. The name of this permission. In most cases the permission name is the same as the associated template name. NotePermission names are generally not unique because they describe types of authorization that may appear in many places throughout the application. |
|
Detail Values |
Display only. Additional detailed information that, when taken with the permission name, defines the permission's function. |
|
Granted to Roles |
Display only. The roles (i.e., the namespace and name of each role) associated with this permission. In some cases multiple roles may be associated with the same permission. To view the Role Inquiry, click the linked name of the desired role. |
This tab identifies the route nodes associated with this document type and displays critical information about the KIM responsibilities associated with them.
On this tab, the system displays route nodes in the order in which the document passes through them. The system also displays responsibility information for the Exception Routing node that will be invoked for this document type only if the document encounters an error that prevents it from completing its normal routing.
 |
Responsibility information is presented for each route node in a standard format.
Workflow / Responsibilities tab definition
|
Title |
Description |
|
Required |
Display only. A Yes or No value that indicates whether this responsibility must generate action requests for this document type. If the value is 'Yes' and the document generates no requests associated with this responsibility, then the document goes into exception status. If the value is 'No' and the responsibility generates no action requests, the document continues to route as normal. |
|
Action Details at Role Member Level |
Display only. A Yes or No value that indicates where the details of this workflow action request are defined. If the value is 'Yes,' the system collects action details when members are assigned to the role. If the value is 'No,' the system collects action details when this responsibility is assigned to a role. |
|
Granted to Roles |
Display only. The roles (that is, the namespace and name of each role) associated with the responsibility at this route node. To view the Role Inquiry, click the linked name of the desired role. |
|
Inherited |
Display only. Indicates whether this responsibility is inherited from another document type. If the value is 'No,' the responsibility is specifically associated with this document type. If a document type name appears here, the responsibility is inherited from the specified document type. To view the Document Configuration Inquiry for this document type, Click the linked name. |
