Maintenance Documents
This topic covers usage of the maintenance e-docs that are accessible via the links in the menu groups appearing on the Maintenance menu screen. It includes subtopics for all maintenance documents, and each is arranged alphabetically within each menu group section, as it is in the user interface.
Where possible, unique section fields are defined and graphics of test environment screen captures are provided to enhance your understanding of each maintenance document’s purpose and usage.
|
|
About the screen shot example data: KC Maintenance Documents are for the most part configurable by implementing institution. Some are delivered with pre-populated, generic or “bootstrap” data that can be used as-is or modified to suit your institution’s unique needs. When possible, the screen shots in this user documentation show populated fields that demonstrate acceptable input. Additionally, the Example subtopic sections for each maintenance document topic section include lookup result values from the demonstration data used in test environments. It does not necessarily reflect actual practice at any particular institution, and is provided merely to give you an idea of how each maintenance document might be used. You will see ‘Old’ and ‘New’ columns due to example screen shots created from editing existing records in order to show “real world” example data rather than blank fields from creating new maintenance documents. |
What Are Maintenance Documents? They are user-defined reference tables that define attributes the system uses for validation and to allow users to look up values. These tables also control the relationship between elements for internal and external reporting. This table-controlled flexibility is one of the key features that make KC a highly configurable application.
What Are Menu Groups? They are boxed in groups of links to documents that are functionally-related. Each typically contains bullet lists of links to lookup screens containing [create new] buttons. Some group boxes are further categorized by menu group section headings in bold type.
|
|
Maintenance Document Permissions: All users have the ability to look up values in KC reference tables by using the lookup screens for each maintenance document. Depending on your implementation, it is likely that the ability to create new (initiate) and edit existing maintenance documents is reserved for those assigned to a System Manager type of role. |
Figure 752 KC Maintenance Menu Screen
Click a Group column link in the following table to go directly to the subtopic for each group on the Maintenance menu to read detailed documentation about the group and each maintenance document within it.
Table 427 Maintenance Menu – Group Descriptions
|
Group (linked to topic) |
Brief Description |
|
Links to maintenance e-docs used to maintain information that is shared by multiple documents and/or across multiple functional modules. | |
|
Links to maintenance e-docs used to maintain information that does not easily lend itself to being categorized into the shared or functional module groups. | |
|
Links to maintenance e-docs used to maintain information that is functionally a part of the Proposals module, and used in the proposal-related e-docs. | |
|
Links to maintenance e-docs used to maintain information that is functionally a part of the Awards module, and used in the award-related e-docs. | |
|
Links in a bullet list that take you to Lookup screens that allow you to either search for existing maintenance e-docs of this type, or create new ones by clicking a button. These are maintenance documents that are used to maintain information that supports and is used by the Negotiations e-doc. | |
|
Links in a bullet list that take you to Lookup screens that allow you to either search for existing maintenance e-docs of this type, or create new ones by clicking a button. These are maintenance documents that are used to maintain information that supports and is used by the Subaward e-doc. | |
|
Links to maintenance e-docs used to maintain information that is functionally a part of the Compliance – Conflict of Interest module, and used in its e-docs. | |
|
Links to maintenance e-docs used to maintain information that is functionally a part of the Compliance module, and used in its e-docs such as Protocol and Committee. |
Shared