About Release Notes

Apttus Release Notes contain the following information about X-Author for Contracts 2.0 Spring 2020 Release on Salesforce.

For more information on new features, enhancements, and document improvements refer to What's new in X-Author for Contracts 2.0 on Salesforce Spring 2020 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 Apttus X-Author for Contracts 2.0 package is automatically upgraded to the latest release without any intervention. Apttus Contract Management (dependent package) is required to be upgraded to this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (New) are new packages in this release.


Latest Certified Version

Version Name | Version Number

X-Author for Contracts (New)2001

Conga Contract Lifecycle Management (New)

11.0.0519 | 11.519

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

New customers must reach out to Apttus Release Management to access X-Author Contracts for Cloud Pre-Release.

System Requirements and Supported Platforms

The following table lists the minimum requirements for installing and using X-Author for Contracts 2.0.

System RequirementMinimum Supported Version
Mac OSmacOS Mojave (Version 10.14.5)
Microsoft Office16.34

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

New Features

The following feature is new in this release.

Support for Office 365

X-Author for Contracts 2.0 provides beta support for Office 365 online and is open to a limited audience. If you have any queries or you want to know more about the feature, please contact Apttus Product Management.


There are no enhancements in this release.

Resolved Issues

The following table lists the issues resolved in this release.

Apttus Internal ID


While marking a clause, the Replace the current clause selection with the one from the library? checkbox label was incorrectly displayed.

The following table lists the issue resolved from the previous releases.

Apttus Internal ID


XAJS-2036Selecting a marked clause and clicking Unmark Clause is not unmarking the clause.

Known Issues

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

Apttus Internal IDIssue
XAJS-3411After exiting and reopening MS Word, X-Author button is not available on the Home tab.
XAJS-2543On clicking Highlight option, the smart and read-only fields are highlighted thrice when Insert Comments and Track Changes protection is applied while generating the document.
XAJS-3386On performing Update from CLM and Preview Reconcile, the Contract date format in Croatian is converted to an invalid date.
XAJS-3367XAJS Template does not support fourth-level Reference fields.
XAJS-3272After deleting the locale from Contract Management, template name and locale are removed in the Check-in page.

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.
XAJS-3077When you Mark Conditional Segment, the field level validation is failing for Less Than and Not Equal To operator for the date field.
XAJS-3061After marking a clause containing Read-Only fields and navigating to the Update From CLM screen, few fields are displayed as modified.

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.

The generated document does not inherit segment styles from the template for marked clauses.

XAJS-2468The Check-in page does not respond after marking a clause with a managed smart field.

The Select Styles window is not displaying custom styles.

XAJS-2771On adding a style segment to a clause, the complete clause is displayed as a Style Segment along with the selected text from the clause.
XAJS-2516Inserting the nested clause is disorganizing the clauses on the Doc Clauses tab.
XAJS-2700A few built-in style segments are not applying in the generated document.
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.


When you check out a document in the ICTC protection mode and mark existing smart fields as clauses and navigate to check in, the XAJS pane stops responding.

Workaround: After checking out a document, unprotect the document and make the necessary changes and check-in. This retains the ICTC mode.

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.
XAJS-2586Navigating from one tab to another is taking longer in large documents.


Make Conditional popup, that appears on clicking Set Segment, stops responding after adding the 10th row.


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

XAJS-2385On reconciling an agreement containing Date fields, the reconciliation screen shows all the Date fields as deleted.
XAJS-2372After checking in an agreement document containing Read Only fields, the X-Author pane stops responding.

Apttus Copyright Disclaimer

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.