Release Notes contain the following information about X-Author for Contracts Spring '21 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
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.
|Product||Latest 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.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)) (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
The following table lists the minimum requirements for installing and using X-Author for Contracts on the Windows operating system.
|System Requirement||Minimum Supported Version|
|Windows Operating System||Windows 10|
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 Requirement||Minimum Supported Version|
|Mac Operating System||macOS Mojave (version 10.14.5)|
|Microsoft Office||Microsoft 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.
The following feature is new to X-Author for Contracts in this release.
Install X-Author for Contracts Add-in using Microsoft AppSource
Now, X-Author for Contracts add-in is available on Microsoft AppSource. You can install the X-Author for Contracts as a Microsoft Word add-in on Mac or Windows operating system.
For details on installing X-Author for Contracts, refer to Installing Production X-Author for Contracts, in X-Author for Contracts User Guide.
The following enhancements are new to X-Author for Contracts in this release.
Ability to Create Alternate Clause
You can tag a clause as an alternate clause while creating a template from X-Author for Contracts.
For details on creating an alternate clause, refer to Creating New Templates in X-Author for Contracts User Guide.
Ability to Clone Alternate Clause
You can tag a clause as an alternate clause while cloning a template from X-Author for Contracts.
For details on cloning an alternate clause, refer to Cloning a Template in X-Author for Contracts User Guide.
Ability to Refresh Intelligent Discovery Status
You can view the intelligent discovery processing status by clicking the Review Import Result in X-Author for Contracts.
For details on the intelligent discovery, refer to Intelligent Discovery in X-Author for Contracts User Guide.
Review Doc Fields after Intelligent Discovery
You can review all the extracted fields in the Doc Fields tab. It shows the actual and normalized values for each extracted field. You can edit a normalized value or set a custom value for a field.
For details on reviewing doc fields after intelligent discovery, refer to Review Doc Fields after Intelligent Discovery in X-Author for Contracts User Guide.
Enhanced Intelligent Discovery Data Processing
When you review a document that was imported using intelligently discovery, you can view the currency, date, term values in the standard format.
For details on reviewing a document, refer to Reviewing Doc Fields after Intelligent Discovery in X-Author for Contracts User Guide.
The following table lists the issue resolved in this release.
|Case Number||Conga Internal ID||Description|
When a user sent an agreement document for parallel review from X-Author for Contracts, the agreement status did not change to "Other Party Review".
The following table lists the issues resolved from the previous releases.
|Conga Internal ID||Description|
|XAJS-4241||When you inserted a clause as smart in an agreement document and checked in the document with the Reconcile option, Inserted and Modified clause actions were added in the Agreement Clause related list.|
|XAJS-4583||When you marked a smart field for removal and checked in the agreement document with the Reconcile option, the smart boundaries and strikethrough were retained in the document.|
The following table provides the cumulative list of known issues up to this release.
|Conga Internal ID||Description|
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:
|XAJS-3386||On 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-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.|
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.|
|XAJS-2516||Inserting a nested clause disorganizes the clauses on the Doc Clauses tab.|
|XAJS-2700||A few built-in style segments do not apply in the generated document.|
|XAJS-2769||The Select Styles window is not displaying custom styles.|
|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.
|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.|
Updating a clause for the second time is not appearing in the Refresh Clauses tab.