Release Notes contain the following information about X-Author for Contracts Winter '20 Release.
For more information on new features, enhancements, and document improvements refer to What's New in X-Author for Contracts Winter '20 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. 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)
Conga Contract Lifecycle Management (New)
11.2.0582 | 11.582
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.
Introducing X-Author for Contracts for Conga CLM (Contracts for Salesforce)
With this release, X-Author for Contracts introduces support for Conga CLM (Contracts for Salesforce). Using X-Author for Contracts, the Conga CLM (Contracts for Salesforce) users can manage and streamline the entire contract template lifecycle within Microsoft Word. As a Conga CLM (Contracts for Salesforce) user, you can perform the following actions when working with X-Author for Contracts:
You can create a new contract template within Microsoft Word using the X-Author for Contracts add-in. Contract templates are stored within the Template object and are used to create contracts.
For details on creating a new template, refer to Creating Templates in X-Author for Contracts Winter '20 User Guide.
This feature allows you to search for contract templates using keywords, text, or template name. You can use the basic search filters to narrow down the search results and download the individual templates that match your search criteria. You can open and modify the downloaded templates.
For details on searching and modifying a template, refer to Opening a Template in X-Author for Contracts Winter '20 User Guide.
After you create a new template or make changes to an existing template, you can check in the template to update its content in Conga CLM (Contracts for Salesforce).
For details on checking in a template, refer to Checking in a Template in X-Author for Contracts Winter '20 User Guide.
You can insert fields in your template. Fields represent the contractual terms and metadata from your Contract Agreement record in Conga CLM (Contracts for Salesforce). When you generate a contract document, the values of the fields are retrieved from the agreement record and populated in the document.
For details on inserting fields in a template, refer to Inserting Fields in Templates in X-Author for Contracts Winter '20 User Guide.
This feature allows you to define the property of the fields. You can either make a field as smart or read-only.
You can insert fields as a table in your template. The table is inserted into your template as a Repeat Table, meaning each separate line item record is populated as a row in the table, with field data populated in individual cells by column.
For details on inserting fields in a template as a table, refer to Inserting fields in Templates as a Table in X-Author for Contracts Winter '20 User Guide.
This feature allows you to make any or all of the columns and rows in a table as conditional. While creating a template, you can define various condition expressions on columns and rows of a table. These condition expressions are evaluated to include or exclude the columns and rows.
For details on making column and row conditional in a table, refer to Making Table Columns and Rows Conditional in X-Author for Contracts Winter '20 User Guide.
You can insert fields as a section in your template and the inserted section is added as a repeat section. This inserts each specified field on a new line when you select multiple fields.
For details on inserting fields in a template as a section, refer to Inserting fields in Templates as a Section in X-Author for Contracts Winter '20 User Guide.
Clause Library contains clauses and clause bundles that are created in the Conga CLM (Contracts for Salesforce). You can use the Clause Library to insert clauses and clause bundles in your template.
For details on using Clause Library for templates, refer to Using Clause Library for Templates in X-Author for Contracts Winter '20 User Guide.
This feature allows you to define the property of the clauses and clause bundles. You can make a clause and clause bundle as smart in your template. Clauses and clause bundles that you insert into your template are marked as smart by default. The clauses within a clause bundle and sub clauses related to clause configuration are also marked as smart by default.
For details on making clauses smart in a template, refer to Making Clauses and Clause Bundles Smart in a Template in X-Author for Contracts Winter '20 User Guide.
This feature allows you to define the conditions for clause and clause bundles to make more customized and flexible contract templates. The condition for the condition-based clauses and clause bundles can be simple or complex expressions that you can make using the expression builder. The conditions are evaluated at the time of agreement document generation and the clause configuration is included in the generated document only if the associated condition resolves to True.
For details on making clauses and bundles conditional in a template, refer to Making Clauses and Clause Bundles Conditional in a Template in X-Author for Contracts Winter '20 User Guide.
This feature allows you to either set a segment conditional, style, or both for the highlighted text in your agreement template. You can define the condition for the segment's visibility using the expression builder. You can use this feature to create a template that can show or hide different segments of text in the generated agreement document based on the conditions set by you.
For details on setting segment in a template, refer to Setting Segment in Templates in X-Author for Contracts Winter '20 User Guide.
Template localization is a feature that allows you to define the locale of your templates. Locales can be system defaults or user-defined locales. You can define locale settings at the contract template and field level. The localization feature allows you to define locale settings for number and currency precision, currency format, and date format.
For details on using template locale, refer to Using Template Locale in X-Author for Contracts Winter '20 User Guide.
There are no enhancements in this release.
The following table lists the issues resolved in this release.
Conga Internal ID
When a user inserted and modified the clause in an agreement document and checked in the document, Modified clause action was not added to the Agreement Clause related list. This behavior was observed when the user reordered the clauses by removing a clause and inserting the same clause at a different location in the document.
When a user checked in a document with Final-to be signed option selected, the PDF file was not created in the Notes & Attachments related list. A user with permissions other than System Administrator observed this behavior on Mac operating system.
The following table lists the issues resolved from the previous releases.
Conga Internal ID
A user encountered the following errors when tried to make a segment conditional in a template:
|XAJS-4471||When a user marked the selected content as a clause that included smart fields and checked in the agreement document, Inserted and FieldChangeOnly clause actions were added to the Agreement Clause related list.|
|XAJS-3367||XAJS Template did not support fourth-level Reference fields.|
When a user marked a clause that included read-only fields and navigated to the Update from CLM screen, few fields were displayed as modified.
|XAJS-2468||When you checked out an agreement document in the ICTC protection mode and marked existing smart fields as clauses and navigated to the check-in page, check-in of the document failed.|
When you checked out an agreement document in the ICTC protection mode and marked existing smart fields as clauses and navigated to check-in, the XAJS pane stopped responding.
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.
|XAJS-4583||When you mark a smart field for removal and check in the agreement document with the Reconcile option, the smart boundaries and strikethrough are retained 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).
|XAJS-4241||When you insert a clause as smart in an agreement document and check in the document with the Reconcile option, Inserted and Modified clause actions are added in the Agreement Clause related list.|
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.