Below is a list of the Contract Attributes that are a part of every UCM System.
For a full Glossary of all terminology for UCM, click HERE.
Notifications set on a per-Contract basis for a specific date that is set at the creation of the Alert. Can be reoccurring, but NOT marked as completed. This is an optional feature that not all systems will have enabled.
Is activated through Workflow (even the most basic). “Hides” your contract from normal system use, but can still be found by checking the “Include Archive” checkbox for all Global Searches and Views.
A unique, system generated ID number. Used most often in support to help verify that any issues we are investigating are for the correct Contracts.
A custom name entered each time you create a new Container.
Created by Admins, it allows you to select any number of Field Groups to be on display, and ready to be filled in, immediately upon creation of the Container. Can also have a specific Workflow attached by default. Contract Type is also used in setting up Milestones and creating Views. *Required for system use.
The security model inside UCM. Each Contract Container must be placed in a Folder when it is created. Users are granted different levels of permissions to the custom folders you create depending on how you wish to control user visibility. NOT to be used for general reporting purposes. Strictly meant to be Security based. Custom fields and other system attributes will handle any reporting that you may have previously used folders for before you purchased UCM.
The Primary or main document listed for a Contract by Full-Access or Administrative users will show in a large area above the Attachments Grid. This depends on your organization, but it is often used to point you towards the governing document for a Contract. For any document on the Attachments tab, you can download the document by clicking on the Current File name (depending on permissions) or edit the document online if this is the most recent version of the document.
Related Contracts can be linked/unlinked from the chosen Contract Container. Users can do this from the Summary Tab under Contract Attributes, when adding a new contract manually or using a template, and from the Related Contracts tab within the Container.
An ad-hoc feature similar to Workflow Approvals. Can only be sent out once and has no Re-occurrence option.
A User who is assigned to review a Contract Container. As opposed to an Approver, who is a part of a previously set-up Workflow, a Reviewer can be added quickly, ad-hoc, to a Container. However, unlike an Approver, once they approve or reject their review, they would have to be manually sent another Review, as opposed to an Approver, who would automatically receive any notification if their assigned Stage was reached again.
An individual piece of a Workflow. Each Stage can be custom named, and they all have the optional features of individually assigning Users to be notified/approve, enabling Field Groups to appear in the Summary Data when a Stage is reached, have custom reminder and escalation emails sent out to the Assignee's, and many other options.
Can refer to anyone of the following: Owner, Primary, Secondary, Tertiary Responsible Parties. A Title can be assigned to receive Notifications, Reports, Views, etc. and then each individual Contract Container can have Named Users assigned to those Titles for more flexibility.
The feature of UCM that helps get your contracts to an active state. Workflows are made up of Stages, that can each have individual settings. Workflows can also be applied to a Contract Type, so the correct Users and departments are always getting notified along the Contracts life-cycle.