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
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
|Apttus X-Author for Contracts 2.0 (New)||2001|
|Apttus Contract 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 Requirement||Minimum Supported Version|
|Mac OS||macOS Mojave (Version 10.14.5)|
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.
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.
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-2036||Selecting a marked clause and clicking Unmark Clause is not unmarking the clause.|
The following table provides the cumulative list of known issues up to this release.
|Apttus Internal ID||Issue|
|XAJS-3411||After exiting and reopening MS Word, X-Author button is not available on the Home tab.|
|XAJS-2543||On 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-3386||On performing Update from CLM and Preview Reconcile, the Contract date format in Croatian is converted to an invalid date.|
|XAJS-3367||XAJS Template does not support fourth-level Reference fields.|
|XAJS-3272||After 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-3054||After 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-3022||Incorrect values are displayed for smart fields after regenerating an agreement with a different template.|
|XAJS-2941||The Compare pane stops responding on changing the value of a smart field in the Current document and comparing it.|
|XAJS-2899||After 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-2885||The currency format for the reference lookup currency field is not displaying as per the record-level currency.|
|XAJS-3077||When you Mark Conditional Segment, the field level validation is failing for Less Than and Not Equal To operator for the date field.|
|XAJS-3061||After 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:
|XAJS-2964||On clicking Reject changes, smart fields are appended with current values instead of replacing the value.|
|XAJS-2931||When 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-2468||The 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-2771||On 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-2516||Inserting the nested clause is disorganizing the clauses on the Doc Clauses tab.|
|XAJS-2700||A few built-in style segments are not applying in the generated document.|
|XAJS-2638||The 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-2703||If 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-2586||Navigating 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-2385||On reconciling an agreement containing Date fields, the reconciliation screen shows all the Date fields as deleted.|
|XAJS-2372||After checking in an agreement document containing Read Only fields, the X-Author pane stops responding.|
Apttus Copyright Disclaimer
DOC ID: XAJSSFSPR20RNREVB20200409