Download page X-Author for Contracts August '22 Release Notes.
X-Author for Contracts August '22 Release Notes
This documentation may contain descriptions of software features that are optional and for which you may not have purchased a license. As a result, your specific software solution and/or implementation may differ from those described in this document. Please contact your Customer Success Manager (CSM) or Account Executive (AE) for information on your specific features and licensing.
All Conga customers have FREE access to getting started content and release training in the Conga Learning Center. To take your training further, ensure your organization has access to the Conga Learning Pass, which is a training subscription service. Click here to learn more.
The X-Author for Contracts package is automatically upgraded to the latest release without any intervention. Conga Contract Lifecycle Management (dependent package) must be upgraded to this release. Prerequisites for each feature can be found in its documentation. The packages marked (New) are new in this release.
|Product||Latest Certified Version (Version Name | Version Number)|
Conga Contract Lifecycle Management (New)
(Required if you are using Conga Contract Lifecycle Management)
13.0.669.03 | 13.669.3
The previous two (n – 2) versions of Conga Contract Lifecycle Management are also supported.
Conga CLM (Contracts for Salesforce) (Required if you are using Conga CLM (Contracts for Salesforce))
System Requirements and Supported Platforms
For requirements and recommendations to consider before installing the Conga product suite, see System Requirements and Supported Platforms Matrix.
The following feature is new to X-Author for Contracts in this release.
Adding Keywords or Tags
You can now add keywords or tags while checking in an agreement document. These keywords can be used to search agreement documents during check-out. For more information, see Checking in an Agreement Document.
The following enhancement is new to X-Author for Contracts in this release.
Retaining Redlines after Unprotecting Document
After unprotecting a document, all the changes that were made before unprotecting are retained as redlines. For more information, see Protecting and Unprotecting Document.
The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.
|Case Number||Conga Internal ID||Description|
|00800712||XAJS-5872||Checking in a template takes more time and sometimes fails.|
|00800930||XAJS-5859||After comparing two documents versions, the compared document does not open in a new Microsoft Word instance.|
The following table provides the cumulative list of known issues up to this release.
|Conga Internal ID||Description|
Inserting a clause as text in a document, unprotecting the document, and checking it in does not add the "InsertedasText" entry for the clause in the agreement clause list.
|XAJS-5867||The clauses that get marked after Review Import Results are marked as deleted with content control border.|
After clicking the Insights menu, the Insights pane is blank.
Workaround: Reload the X-Author for Contracts pane to view the InSights details.
The extracted fields and clauses using the Insights option that are not marked in X-Author for Contracts due to overlapping extractions display additional insights.
|XAJS-5800||Generating an agreement document that has conditions for segments inside a repeat table is not validated.|
Updating fields from CLM in an agreement document that contains repeat tables with conditions fails to display the updated field values.
Editing text or a smart field in the first paragraph of a document sent for external review using Office 365 results in an error message.
Inserting a clause (containing segments) without applying formatting inside a numbered or bulleted list of a template inserts a blank numbered or bulleted line after the clause.
Workaround: Delete the blank numbered or bulleted line manually.
Refreshing a clause that has a conditional segment retains the clause, but removes the conditional segment associated with the clause.
Workaround: Add a line break before the clause inside the segment, and then refresh the clause.
Using the Delete button to delete a field from an open agreement document containing read-only fields works in Microsoft Word 16.54, but not in Word 16.47.
|XAJS-5256||Checking out an older version of an agreement document that is in pending approval status does not display the lock message.|
|XAJS-5176||The Spanish date format dd MMM yyyy populates the Date field differently in CLM and X-Author for Contracts.|
If a template's name contains special characters, they are replaced with spaces. In Conga CLM, however, special characters are not replaced, and the template name is saved as-is.
With X-Author for Contracts for Conga CLM (Contracts for Salesforce), setting a style for a segment containing clauses or clause bundles does not apply the selected style to the clauses or clause bundles in the agreement document.
The formatting of the bulleted list is not proper when you:
The Update from CLM and Preview Reconcile actions convert the contract date to an invalid date format in Croatian.
Generating an agreement using a non-localized template adds a currency prefix symbol to the currency data type field.
Workaround: Set the APTS_DoNotPrefixCurrency admin entry to true while generating agreement documents.
When you change the value of a smart field in a document and compare it, the compare pane stops responding.
|XAJS-2885||The currency format for the reference lookup currency field is not displaying as per the configured record-level currency.|
Clicking Reject Changes appends current values to smart fields instead of replacing them.
|XAJS-2700||Some built-in style segments do not apply in the generated document.|
DOC ID: XACAUG22RN20220803