The Document Type Hierarchy is a visual that shows the different document types and their permissions, responsibilities and roles. Financials leverages inheritance by assigning documents to parents, grandparents, up through the chain. This allows us to assign permissions at a high level to grant access to all and then to create permissions or responsibilities at a lower level to restrict access without having to create separate permissions for all the things that are the same for all documents. Refer to Document Type for information on creating new document types.
Document Type Hierarchy
When you Jump to Document Type Hierarchy, you are presented with two tabs. Kuali Document and Financial System - Ledger Only (FSLO).
- The Kuali Document tab displays all the Documents that can be accessed from the UI grouped by their parent and grandparents.
- The FSLO Document tab displays all the Document Types that are used for posting entries created by other processes or external systems. Following are some examples of FSLO entries:
- Entries submitted by Internal Billing Units
- Check and ACH entries created by Pre-Disbursement Processor to clear liabilities or post expenses
- Entries submitted by other enterprise systems, such as Payroll and Student.
- Entries created when asset depreciation is run.
- Entries created when year end batch jobs are run.
The small text under the blue lettering represents the route nodes contained on the document. In addition to the listed route nodes, all documents have exception routing. In the event that workflow can't determine where to send a document, it will route to exception to be resolved by workflow administrators.
In the above screenshot - Cash Receipt doesn't have any route nodes and does not route, DV has several route nodes as does DI.
To view a documents configuration - permissions, responsibilities aka workflow and role assignments. Click on the ellipses next to the document.
Click on View Document Configuration.
The Document Information tab contains information about the document and it's relationship to other documents. It's Parent and Children, if any.
The permissions tab show the permissions defined for the Document and any permissions that are inherited from its Parent, it's Parents Parent and so on up until it gets to Kuali Document.
- If a finer grained permission has been created for any document lower in the hierarchy, the higher permission will be stricken through. In the screenshot above. Initiate Document ARM is stricken through because a permission has been defined for this document - Initiate Document CUS.
- The roles that have been assigned each permission are listed as well. This helps you determine who can do what.
Workflow / Responsibilities
The Responsibilities aka Workflow tab detail which role is assigned to each Responsibility.