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.
To access the learning path, including overviews and demonstrations of this release’s updated features and enhancements, visit the Conga Learning Center.
The following X-Author for Contracts package is automatically upgraded to the latest release without any intervention. Conga Contract Lifecycle Management (dependent package) is required to be upgraded to this release. Separate prerequisites for each feature can be found in the respective documentation. The packages marked as (New) are new in this release.
|Product||Latest Certified Version (Version Name | Version Number)|
X-Author for Contracts (New)
Conga Contract Lifecycle Management (New)
(Required if you are using Conga Contract Lifecycle Management)
13.0.669 | 13.669
The previous two (n–2) versions of Conga Contract Lifecycle Management are also supported.
Conga CLM (Contracts for Salesforce) (New) (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 features are new to X-Author for Contracts in this release.
View and Replace Alternate Clauses
This feature allows you to view the already predefined alternate clauses that are associated with the standard clause and replace them during the negotiation process. For more information, see Viewing and Replacing Alternate Clauses.
External Review Using Office 365
This feature allows the external reviewer to review a document initiated from CLM using Office 365. The document can be reviewed and edited online. For more information, see External Review using Office 365.
Internal Review Using Office 365
This feature allows the reviewer to review a document that was sent from CLM using O365, using X-Author for Contracts. This option also allows the contract negotiator to make a final review and check in the document. For more information, see Internal Review using O365.
Extracting Agreement Data Using Contract Intelligence for CLM
This feature allows you to view the extracted key data from an agreement document. After data extraction , you can edit the extracted fields and clauses reconcile it. For more information, see Extracting Agreement Data Using Contract Intelligence for CLM.
The following enhancements is new to X-Author for Contracts in this release
Revamp of All User Interface (UI) Messages
Edited the following UI messages to provide clarity and understanding for users:
- Success messages
- Validation messages
- Confirmation messages
- Error messages
- Warning messages
- Unhandled exception messages
- API messages
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|
|00783449||XAJS-5440||When an agreement document is in change tracking mode and you press the delete or backspace key to delete a smart field in the document, X-Author for Contracts displays an error message.|
|00775072||XAJS-5419||When you add a conditional segment to a field inside a repeat table, X-Author for Contracts displays an error message.|
|00790552||XAJS-5687||When you check in a document, X-Author for Contracts displays an error message.|
|NA||XAJS-5640||After you create a new conditional segment for a particular field in a template, instead of displaying the field name, X-Author for Contracts displays the text "Click or tap here to enter text".|
The following table provides the cumulative list of known issues up to this release.
|Conga Internal ID||Description|
|XAJS-5619||When you open a document for external review sent using the Office 365 feature, you are unable to edit the text or smart field in the first paragraph of the document.|
When you refresh a clause that has a conditional segment, the conditional segment associated with the clause gets removed and only the clause remains.
Workaround: Add a line break before the clause inside the segment, and then refresh the clause.
|XAJS-5315||When you open an agreement document that contains read-only fields and press Delete to delete the field, the filed is deleted in the latest Microsoft Word 16.54 version, however it is not deleted in Microsoft Word version 16.47.|
|XAJS-5256||When you check out an older version of an agreement document in pending approval status, the lock message is not displayed.|
|XAJS-5176||The Spanish date format dd MMM yyyy is populating 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.
When working with X-Author for Contracts for Conga CLM (Contracts for Salesforce), if you set a style for a segment that contains clauses or clause bundles, the selected style does not apply 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.
When you generate an agreement using a non-localized template, a currency prefix symbol is added 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.
When you create a section and a third-level table, then navigate to the Update from CLM screen, the values of smart fields appear as changed even if there were no changes made to smart fields.
|XAJS-2885||The currency format for the reference lookup currency field is not displaying as per the record-level currency.|
On validating doc fields after deleting smart and merge fields, an error is displayed.
When you click Reject Changes, current values are appended to smart fields instead of replacing them.
|XAJS-2516||Inserting a nested clause disorganizes the clauses on the Doc Clauses tab.|
|XAJS-2700||Some built-in style segments do not apply in the generated document.|
|XAJS-2703||If an agreement document has any read-only lookup fields in the repeating table under the repeat section, the XAJS pane stops responding using the Update from CLM option.|
DOC ID: XACMAY22RNREVB20220503