Release Notes contain the following information about X-Author for Contracts Summer '21 Release.

For more information on new features, enhancements, and document improvements, refer to What's New in X-Author for Contracts Summer '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 in this release.

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

12.0.0630 | 12.630 

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


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

Microsoft 365 is a prerequisite to install and run X-Author for Contracts on Windows and Mac operating systems.

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

Microsoft 365 version from 16.0.11629 to 16.0.13231.20262

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 365 version from 15.32 to 16.51 

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

The following features are new to X-Author for Contracts in this release. 

Re-marking the extracted fields

In this release, users now have the ability to re-mark the extracted fields and lookup fields while reviewing them in the Doc Fields tab.

Get Started

For detailed information on re-marking the extracted fields and lookup fields, refer to Reviewing Doc Fields after Intelligent Discovery in the User Guide.

Deleting the extracted fields

In this release, users now have the ability to delete the extracted fields and lookup fields while reviewing them in the Doc Fields tab.


The following section describes existing features that are changed (or are no longer supported) in this release.

Enhancements to User Interface

The UI of the following pages is enhanced in both Conga CLM and Conga CLM (Contracts for Salesforce) for a better user experience. 

User InterfaceEnhancement
Side Navigation MenuEnhanced to better reflect and access features such as Contracts, Templates, Documentation, TechSupport, and App details
Creating a New TemplateThe button label 'Save' has been changed to 'Create New'
View VersionsEnhanced for a better user experience
Insert FieldsThe flow of inserting fields is enhanced for a better user experience
Field and Clause properties on the landing pageEnhanced for a better user experience

Condition Icon ()

A lighting icon is introduced in this release to indicate a specific segment or clause is conditional

Opening Templates in the same instance

You can open the required template in the same instance without downloading it.

Get Started

For details on opening a template in the same instance, refer to Opening Templates for Conga CLM and Opening a Template for Conga CLM (Contracts for Salesforce)in X-Author for Contracts User Guide.

Renaming the Playbook to Clause Library

In Summer '21 release, the Playbook is renamed Clause Libray. 

Get Started

For more details, refer to Using Clause Library for TemplateUsing Clause Library for Template in X-Author for Contracts User Guide.

Ability to view all Conditions added to Segments and Clauses

You can view the conditions applied to Clause under Clause name by clicking on the "lightning" icon.

Ability to view field type in Insert Field pop-up window

You can view the field type while inserting a field in a template in Conga CLM and Conga CLM (Contracts for Salesforce).

Get Started

For detailed information on inserting fields in a template, refer to Inserting Fields in a Template in X-Author for Contracts User Guide.

Resolved Issues

The following table lists the issue resolved in this release.

Case NumberConga Internal IDDescription


XAJS- 5027

X-Author for Contracts did not allow marking clause or field on third party paper. A user encountered an error while publishing the document from OCC after accepting all the changes.

NAXAJS-2365The following issues can be observed while working with bullets:
  • When a user inserts a clause containing bullets, the last bullet is removed.
  • When a conditional segment content has bullets, an extra bullet is added at the end of the segment.
  • When there are sub-bullets, an extra bullet is added at the end of sub-bullets.
NAXAJS-4584When the MS Word version is 16.0.13231.20250, the home page in the staging environment does not load.

The following table lists the known issues resolved from the previous 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 insert a clause in a template that contains a Microsoft Word table with a style segment, the check-in of the template takes more than 90 seconds.  


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


On the latest version of Microsoft Word 16.38+ on Mac, the Insert Field pop-up window is displaying on the top right corner. 

Known Issues

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

Conga Internal IDDescription

A user encountered an OAuth error while logging in to the X-Author for Contracts on Microsoft Windows.


  • Refresh the page or enter login credentials again.

If the template's name contains special characters then the special characters are replaced with space. However, the template is saved as is in Conga CLM.


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


On clicking the Highlight option, the smart and read-only fields are highlighted thrice. This happens when you apply for 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-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 the 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-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-2703If 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: XACSUM21RN20210705