Contract Guardian Updates

My friends at Contract Guardian continue to meet the challenge of compliance in complex contractual and regulatory agreements.  Favorite topics of mine.  Check them out.

" .... We have released a few new features in Contract Guardian.  I thought you would be interested in some of these new items.  If you want to see any of these in action, just let me know. . .  " John Reuter



Power Edit
We have just released a new fast edit of multiple agreements meta data concurrently.  Think of it as an online spreadsheet edit.  So you select the contracts you want to edit by entering some search criteria then the system pulls the documents that match the selection criteria.  You pick the fields you want to edit and a grid appears with the documents and fields that match your selection in a grid.  You edit the fields and they are updated at one time.  The edit process, reviews all business rules established at the database level, it journals the changes and performs all the same checks as the single page document edit.  This feature removes a lot of navigation to modify random values across many documents meta data.  To see a full press release, click here.

Version Control
We have added the ability to add, store and access multiple versions of the same document stored on Contract Guardian.  You can access and download any of the previous versions of the document.  This feature is a component of the new workflow document routing which is almost ready to be released. The new document workflow is easy to use and easy to understand with graphics associated with the flow of the document.  More on document routing when it is available.  To see a full press release on version control, click here.

Document Routing
The first phase of this new feature should be available in the next few weeks.  The basic concept is to allow a route to be defined as a route template.  The route contains a series of defined steps.  Steps are like "Approve by Engineering", another step may be "Approve by Management", and another may be "Approve by CFO".  Each step has configuration options for turning off email notices, assigning users and groups of users that are required for approval.  When a document is assigned to a route, it must flow through the route and be approved by each step before it is finally approved.  This is meant to be an internal workflow for controlling changes to the document and the approval process.  More on this shortly.

If you want to discuss any of these items further, just let me know. If you decide to blog any of this email please do not get specific on the Document Routing until that one is released.  ..... "