In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the X-Author for Contracts February'23 release. For documentation updates, see What's New in X-Author for Contracts Documentation.

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.

ProductLatest Certified Version NameLatest Certified Version Number

Conga Contract Lifecycle Management

(Required if you are using Conga Contract Lifecycle Management


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.

New Features

The following feature is new to X-Author for Contracts in this release.

Send Documents for Mixed Review using Office 365

You can now send agreement documents for review for internal and external reviewers at the same time from Conga CLM. The document opens on online Microsoft Word where you edit. For more information, see Mixed Review using Office 365


There are no new enhancements in this release.

Fixed Issues 

The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.

Case NumberConga Internal IDDescription

Enabling APTS_ProfilePermissions custom permissions in the org, blocks other users who have different profile permissions from logging to X-Author for Contracts.


When you mark a number that includes a comma as a currency field, X-Author for Contract displays an error message.


When you check in a redlined document with Reconcile option and then make changes to any fields in CLM, the value of the smart field is redlined but has the previous value from CLM, and the current value of the field is displayed as deleted.

Known Issues

The following table provides the cumulative list of known issues up to this release.

Conga Internal IDDescription

The following X-Author for Contract features are not working when the user is working on Windows 11 Operating System and using either Microsoft Office 2016 or Microsoft Office 2019: Checking in and checking out agreement document, compare and merge, and regenerate.


The following X-Author for Contract features are not working when the user is working on Windows 11 Operating System and using either Microsoft Office 2016 or Microsoft Office 2019: List of fields and insert fields in templates and adding conditional segments.

XAJS-5758Extracting 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-5800Generating 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-5256Checking out an older version of an agreement document that is in pending approval status does not display the lock message. 
XAJS-5176The 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:

  • Make a segment that contains a bulleted list conditional in a template.
  • Mark a clause to a block of text that contains a bulleted list in the template or agreement document. 
  • Insert a clause that contains a bulleted list in the template or agreement document. 

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-2885The 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-2700Some built-in style segments do not apply in the generated document.

DOC ID: XACFEB23RN20230208