Release Notes contain the following information about X-Author for Contracts Spring21.03.12 Release.

For more information on new features, enhancements, and document improvements refer to What's New in X-Author for Contracts Spring '21 User Guide.

  • Packages: Lists packages that are required to upgrade to this release of the product
  • System Requirements and Supported Platforms: Lists requirements and recommendations for installing this release
  • New Features: Provides high-level descriptions of new features introduced in this release, with links to more detailed information
  • Enhancements: Provides high-level descriptions of enhancements to existing features
  • Resolved Issues: Lists customer-reported issues that are resolved in this release or known issues resolved from previous releases
  • Known Issues: Lists known issues that are applicable in this release
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 CSM or AE for information on your specific features and licensing.


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 guides. The packages marked as (New) are new packages in this release.

ProductLatest Certified Version (Version Name | Version Number)

X-Author for Contracts 


Conga Contract Lifecycle Management 

(Required if you are using Conga Contract Lifecycle Management)

12.0.0605 | 12.605 or later

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))


Before installing or upgrading managed packages, you must review the dependency matrix for each managed package. You can refer to the package dependency matrix at Managed Packages Dependency Matrix

System Requirements and Supported Platforms

The following table lists the minimum requirements for installing and using X-Author for Contracts on the Windows operating system.

System RequirementMinimum Supported Version
Windows Operating SystemWindows 10
Microsoft Office

Office 365 versions up to 16.0.11629 version

The following table lists the minimum requirements for installing and using X-Author for Contracts on the Mac operating system.

System RequirementMinimum Supported Version
Mac Operating SystemmacOS Mojave (version 10.14.5)
Microsoft OfficeMicrosoft Office version16.34 or higher 

New features and technologies are continuously deployed in new releases by X-Author for Contracts and they are supported by Conga where the associated Microsoft Office versions are also still supported by Microsoft. As Mircosoft ends its own support for any Office version, subsequent new Conga release will no longer be developed, tested, or committed to support the application, on that version.

New Features

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.

Updates to Review Doc Fields after Intelligent Discovery

For fields with multiple extractions, if you do not explicitly select one of the normalized values from the list, each occurrence of the field is updated with the first normalized value in the document.

Get Started

For details on reviewing doc fields after intelligent discovery, refer to Reviewing Doc Fields after Intelligent Discovery in X-Author for Contracts Spring '21 User Guide.

Enhanced User Interface of Review Import Result

The user interface of the Review Import Result is enhanced to show an indication to edit the extracted fields in the document.

Get Started

For details on updating extracted fields after intelligent discovery, refer to Reviewing Doc Fields after Intelligent Discovery in X-Author for Contracts Spring '21 User Guide.

Ability to Clone Standard Clause as Alternate Clause

You can tag a standard clause as an alternate clause while cloning a template from X-Author for Contracts.

Get Started

For details on cloning an alternate clause, refer to Cloning a Template in X-Author for Contracts Spring '21 User Guide.

UX Enhancements to Fields and Clauses for Templates

The Fields and Clauses tab has a UI enhancement to improve the user experience while inserting fields and clauses.

Get Started

For details on inserting fields and clauses, refer to Templates in X-Author for Contracts Spring '21 User Guide.

Updates to Check-in of Template

You do not need to download the template document after checking in while using X-Author for Contracts for Conga CLM (Contracts for Salesforce). You can continue editing the same document even after check-in.

Get Started

For details on checking in a template, refer to Checking In a Template in X-Author for Contracts Spring '21 User Guide.

Resolved Issues

The following table lists the issues resolved in this release. 

Case NumberConga Internal IDDescription
NAXAJS-4899A user encountered an error while sending an agreement document for parallel review.
NAXAJS-4886A user was unable to preview the generated agreement document from Notes & Attachments related list.

Known Issues

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

Conga Internal IDDescription

When a user compares two agreement documents containing date fields, the read-only date fields are removed and smart date fields are displayed as deleted in the document. 


When you generate an agreement document using a contract template that contains multiple fields, repeat tables, and repeat sections, clauses with multiple sub clauses, and clause bundles with multiple clause configurations, you do not redirect to the agreement detail page after successful agreement generation. The user observes this behavior when working with X-Author for Contracts for Conga CLM (Contracts for Salesforce).  


When 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 user observes this behavior when working with X-Author for Contracts for Conga CLM (Contracts for Salesforce).  


When you insert a clause in a template that contains a Microsoft Word table with style segment, the check-in of template takes more than 90 seconds.  


On clicking Highlight option, the smart and read-only fields are highlighted thrice. This happens when you apply Insert Comments and Track Changes protection while generating a document.


The formatting of the bulleted list is not proper when you perform the following actions:

  • Make a segment that contains a bulleted list conditional in a template.
  • Mark 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. 
XAJS-3386On performing Update from CLM and Preview Reconcile, the Contract date format in Croatian is converted to an invalid date.

When you generate an agreement using a non-localized template, a currency prefix symbol is added to the currency data type field.

Workaround: Set APTS_DoNotPrefixCurrency admin entry to true while generating agreement documents.

XAJS-3054After inserting a smart clause in an agreement, the Conditional Segment within the clause does not appear as per the condition set for the clause.
XAJS-3022Incorrect values are displayed for smart fields after regenerating an agreement with a different template.
XAJS-2941The Compare pane stops responding on changing the value of a smart field in the Current document and comparing it.
XAJS-2899After creating a section and a third-level table and navigating to Update From CLM screen, the values of smart fields appear as changed even if there were no changes made to smart fields.
XAJS-2885The 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 merge two versions of an agreement document generated with two different templates, you can view only revised version changes in the merged document.


The following culture-specific date formats are not supported:


  • ddd d MMMM yyyy (For example, ศ. 20 มกราคม 2560 is displayed for 20/1/2560).
  • 'วัน'dddd'ที่' d MMMM gg yyyy (For example, วันศุกร์ที่ 20 มกราคม พ.ศ. 2560 is displayed for 20/1/2560).
  • Thai dates use Buddhist year which is 543 years ahead. Hence, 2017 is displayed as 2560.


  • el-gr ---- MMMM yyyy (For example, Μάιος 2017 is displayed for May 2017).
XAJS-2964On clicking Reject changes, smart fields are appended with current values instead of replacing the value.
XAJS-2931When an Agreement Status Category or Status is restricted for check-in and check out, the restriction message does not appear for an offline agreement document. The offline document checks in successfully.
XAJS-2516Inserting a nested clause disorganizes the clauses on the Doc Clauses tab.
XAJS-2700A few built-in style segments do not apply in the generated document.
XAJS-2769The Select Styles window is not displaying custom styles.
XAJS-2638The loading time of the Preview Reconciliation window is more than 30 seconds on updating the content.

Using the Hide Smart Boundary option displays the smart boundary on pressing Command+Z.

XAJS-2703If an agreement document has any read-only lookup fields in the repeat table under repeat section, the XAJS pane stops responding on using the Update from CLM option.


Updating a clause for the second time is not appearing in the Refresh Clauses tab.