Release notes for Conga AI Analyze 1.21.1

ALL ITEMS LISTED ARE SUBJECT TO CHANGE ON OR AFTER THE RELEASE DATE

New Features and Enhancements


Blueprint Designer Enhancements

  • The Conga provided blueprints, (Lease, NDA, and Other) are now separated from any custom and/or cloned blueprints in the interface.
  • If you’ve previous modified a blueprint, your modified blueprint(s) moved to the custom blueprints section, and you are provided with the three original blueprint templates in their original states to prevent edits. When you want to make modifications to a Lease, NDA, or Other blueprint, you need to Clone the original blueprint, and make edits to the cloned version.
  • This change allows you to use an unmodified out-of-the-box blueprint in an analysis, and to use the criteria within a Conga blueprint as best practice guidelines when adding criteria to any custom blueprints.
  • You can now delete custom blueprints.
    Warning: This also deletes Salesforce mapping relating to that specific blueprint.


Additional Statuses added to the Analysis Queue

  • Upload in Progress
  • Upload Complete
  • OCR Pending
  • OCR in Progress
  • OCR Complete
  • Analysis Pending
  • Analysis in Progress
  • Analysis Complete
  • CLM Publish Pending
  • CLM Publish Complete
  • CLM Publish Partially Complete
  • CLM Publish Failed
  • Error


Additional Column added to the Analysis Queue

  • Added a new column to the Analysis Queue labeled Last Modified.
  • This column allows you to see the last time a change was made in a particular document (for example, you can see if a clause or field was changed for Machine Learning training purposes, or if you published a document’s data to your Contract Lifecycle Management system).
  • The Analysis Queue is now always sorted by the Last Modified column. If a document is never modified or opened, the Last Modified date reflects the Created Date.


Showing Field Values in the Document Tree

  • You can now see the values for each found field below the field label in the document tree. For example, if the analyzer found a September 1, 2020 Start Date within a document, that value is now displayed underneath the field in the left side column to make quickly reviewing field data a more efficient process.
  • When a user makes a correction to a clause or field or clicks on a clause or field directly, that initiates the Corrections Panel to pop up on the right hand side of the screen. These field values are also now shown underneath all field labels in the Corrections Panel.