Download page X-Author for Contracts January '23 Release Notes.
X-Author for Contracts January '23 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.
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 Name||Latest Certified Version Number|
Conga Contract Lifecycle Management
(Required if you are using Conga Contract Lifecycle Management) (New)
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.
There are no new features in this release. Keep checking the Conga Documentation Portal for new updates.
The following enhancements are new to X-Author for Contracts in this release.
Ability to Mark a Field inside a Clause
While marking fields in an agreement document, you can now mark fields that are inside a clause. For more information, see Doc Fields.
Displaying Lock icon for Read-only fields
When the list of fields are displayed, the read-only fields are identified using a lock icon. For more information, see Doc Fields.
Displaying API Name of the Field
When inserting new fields in template document, hovering over the filed name displays the API name of the field. For more information, see Inserting Fields in a Template.
Disabling Read-only and Smart Property for Fields inside the Header and Footer
The fields inserted in the headers and footer of template document cannot be marked read-only or smart. They are just considered as merge fields. For more information, see Inserting Fields in a Template .
Compare Clause Text
Using this feature, you can compare any plain text or clause in your agreement document with any clause from the Clause Library. For more information see, Comparing Clauses.
The following table lists the issue fixed in this release. If any actions are required, they will be listed in this table.
|Case Number||Conga Internal ID||Description|
When you create conditional segments in templates, X-Author displays the following error message.
The following table provides the cumulative list of known issues up to this release.
|Conga Internal ID||Description|
|XAJS-5758||Extracting clauses using Contract Intelligence for CLM only marks the title of the clause as extracted and omits the remaining clause text.|
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.
After clicking the Insights menu, the Insights pane is blank.
Workaround: Reload the X-Author for Contracts pane to view the InSights details.
Fields and clauses extracted using the Insights option that is not marked in X-Author for Contracts due to overlapping extractions display excessive insights.
|XAJS-5800||Generating an agreement document that has conditions for segments inside a repeat table is not validated.|
When updating CLM fields in an agreement document containing conditionalized repeat tables, the updated field values fail to display.
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 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: XACJAN23RNREVA20230106