Download PDF
Download page 2023.10.0 Release Notes.
2023.10.0 Release Notes
In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the X-Author for Contracts 2023.10.0 release. For documentation updates, see What's New in X-Author for Contracts Documentation.
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 Customer Success Manager (CSM) or Account Executive (AE) for information on your specific features and licensing.
Packages
The X-Author for Contracts package is automatically upgraded to the latest release without any intervention. Conga Contract Lifecycle Management (dependent package) must be upgraded to this release. Prerequisites for each feature can be found in its documentation. The packages marked (New) are new in this release.
Product | Latest Certified Version Name | Latest Certified Version Number |
---|---|---|
Conga Contract Lifecycle Management (Required if you are using Conga Contract Lifecycle Management) (New) | 13.683.17 The previous two (n – 2) versions of Conga Contract Lifecycle Management are also supported. | 13.683.17 |
Conga CLM (Contracts for Salesforce) (Required if you are using Conga CLM (Contracts for Salesforce)) (New) | 2.101 | 2.101 |
System Requirements and Supported Platforms
For requirements and recommendations to consider before installing the Conga product suite, see System Requirements and Supported Platforms Matrix.
New Features
There are no new features in this release. Keep checking the Conga Documentation Portal for new updates.
Enhancements
The following enhancements are new in this release:
Retain Document Name
You now have an option to retain your document name when checking in a document. For more information, see Checking in a Contract Document.
Clause Behavior Option
Clause Behavior was added as a new option during template creation. With this option, you can mark a clause as Default or Delete Read-Only. For more information see Creating New Templates.
Insert Read-Only Clauses in a Template
You can now insert read-only clauses in a template. For more information, see Using the Clause Library for a Template and Making Clauses Delete Read-Only in a Template.
Insert Read-Only Clauses in a Contract
You can now insert read-only clauses in a contract document. For more information, see Using the Clause Library for a Contract.
Rich Text Field Enhancement
Template Administrators now can toggle on and off the Read-Only Field option after inserting the Rich Tex field data type into a template. For more information, see Inserting Fields in a Template.
Clause Marking Enhancements
- Category and subcategory fields on the Mark Clause screen are retrieved from the Agreement Clause object.
- If the Category and Subcategory do not match the Agreement Clause object when promoting a clause from the Template Object, then users must manually select the Category and Subcategory while marking a clause.
For more information, see Marking Clauses.
Clause Promoting Enhancement
Category and subcategory fields are retrieved from the Agreement Clause object when you promote a clause. For more information, see Promoting Clauses to Clause Library.
Repeat Table Enhancement
The Repeat Table user interface now only displays the current object when selecting a row condition.
Watermark Enhancement
The watermark option is now automatically at check-in selected if X-Author for Contracts detects the document uses a watermark. You can deselect this option if you want to remove the watermark from your document. For more information, see Checking in a Contract Document.
Master Profile Permissions
APTS_ProfilePermissions was updated with a Master Profile permission set. For more information, see Assigning Custom Permissions to User Profiles.
Fixed Issues
The following table list the issue fixed in this release. If any actions are required, they will be listed in this table.
Case Number | Conga Internal ID | Description |
---|---|---|
00846482 | CONTRACTS-10252 | User receive an OK Error on the screen when they are either attempting to check-in or clone a template. |
00851497 | CONTRACTS-11577 | Customers receive the error An error occurred while processing your request error when attempting to open and update, check-in, or Navigate to Fields in a contract document. |
00852925 | CONTRACTS-11780 | If a user closes the word without logging out of X-Author for Contracts and X-Author for Contracts undergoes maintenance, then the next time the user tries to launch X-Author for Contract they are not logged in automatically and the add-in gets stuck on a processing spinner. |
00853131 | CONTRACTS-11785 | Marking a new clause with a header is only adding the header to the clause and excluding the text content. |
00856864 | CONTRACTS-12921 | User receive the error An error occurred while processing your request when attempting to check a template in. |
Known Issues
The following table provides the cumulative list of known issues up to this release.
Conga Internal ID | Description |
---|---|
CONTRACTS-13454 | Additional spaces are added to some fields after end review. |
CONTRACTS-12052 | Updating negative fields with positive fields does not display correctly in preview reconcile. If the negative field has multiple instances, then preview reconciliation does not update all fields correctly and throws document validation error. |
CONTRACTS-10627 | Redlined changes in the Agreement Document don't show up correctly in the Edited section when Reconciled. |
XAJS-6191 | The following X-Author for Contract features are not working when the user is working on Windows 11 Operating System and using either Microsoft Office 2016 or Microsoft Office 2019: Checking in and checking out agreement document, compare and merge, and regenerate. |
XAJS-6190 | The following X-Author for Contract features are not working when the user is working on Windows 11 Operating System and using either Microsoft Office 2016 or Microsoft Office 2019: List of fields and insert fields in templates and adding conditional segments. |
XAJS-5758 | Extracting clauses using Contract Intelligence for CLM only marks the title of the clause as extracted and omits the remaining clause text. |
XAJS-5898 | Inserting a clause as text in a document, unprotecting the document, and checking it in does not add the "InsertedasText" entry for the clause in the agreement clause list. |
XAJS-5869 | After clicking the Insights menu, the Insights pane is blank. Workaround: Reload the X-Author for Contracts pane to view the InSights details. |
XAJS-5870 | Fields and clauses extracted using the Insights option that is not marked in X-Author for Contracts due to overlapping extractions display excessive insights. |
XAJS-5800 | Generating an agreement document that has conditions for segments inside a repeat table is not validated. |
XAJS-5836 | When updating CLM fields in an agreement document containing conditionalized repeat tables, the updated field values fail to display. |
XAJS-5619 | Editing text or a smart field in the first paragraph of a document sent for external review using Office 365 results in an error message. |
XAJS-5742 | Inserting a clause (containing segments) without applying formatting inside a numbered or bulleted list of a template inserts a blank numbered or bulleted line after the clause. Workaround: Delete the blank numbered or bulleted line manually. |
XAJS-5150 | Refreshing a clause that has a conditional segment retains the clause, but removes the conditional segment associated with the clause. Workaround: Add a line break before the clause inside the segment, and then refresh the clause. |
XAJS-5315 | Using the Delete button to delete a field from an open agreement document containing read-only fields works in Microsoft Word 16.54, but not in Word 16.47. |
XAJS-5256 | Checking out an older version of an agreement document that is in pending approval status does not display the lock message. |
XAJS-5176 | The Spanish date format dd MMM yyyy populates the Date field differently in CLM and X-Author for Contracts. |
XAJS-4982 | If a template's name contains special characters, they are replaced with spaces. In Conga CLM, however, special characters are not replaced, and the template name is saved as-is. |
XAJS-4531 | With X-Author for Contracts for Conga CLM (Contracts for Salesforce), setting a style for a segment containing clauses or clause bundles does not apply the selected style to the clauses or clause bundles in the agreement document. |
XAJS-2365 | The formatting of the bulleted list is not proper when you:
|
XAJS-3386 | The Update from CLM and Preview Reconcile actions convert the contract date to an invalid date format in Croatian. |
XAJS-3301 | Generating an agreement using a non-localized template adds a currency prefix symbol to the currency data type field. Workaround: Set the APTS_DoNotPrefixCurrency admin entry to true while generating agreement documents. |
XAJS-2941 | When you change the value of a smart field in a document and compare it, the compare pane stops responding. |
XAJS-2885 | The currency format for the reference lookup currency field is not displaying the configured record-level currency. |
XAJS-2964 | Clicking Reject Changes appends current values to smart fields instead of replacing them. |
XAJS-2700 | Some built-in style segments do not apply in the generated document. |
DOC ID: XAC2023.10.0PRN202301004