In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for X-Author for Contracts 1.0 (previously known as X-Author Contracts) Spring20.04.06 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 CSM or AE for information on your specific features and licensing.

Packages 

The following packages and dependencies are required to upgrade to this release and use its new features. These are the minimum required versions; later versions are also supported. Prerequisites for each feature can be found in its documentation. Packages marked (New) are new for this release.

Product

Latest Certified Version

Version Name | Version Number

X-Author Contracts (New)

11.29.0315 | 11.29.315

Conga Contract Lifecycle Management 

13.0.669 | 13.669

System Requirements and Supported Platforms

X-Author for Contracts 1.0 is a Microsoft Word add-in that you can access from a Windows machine. After your system administrator installs the X-Author for Contracts 1.0 add-in on your Salesforce Org, install your local instance of the add-in. 

  • You cannot use X-Author for Contracts 1.0 with macOS; however, you can use it with a Mac running a Windows virtual machine in a Citrix environment.

  • X-Author for Contracts 1.0 only works in a Windows desktop environment. 
  • New X-Author for Contracts 1.0 features and technologies are continuously deployed, and Conga supports them as long as Microsoft supports the associated Windows and Office versions. As Microsoft ends its support for any Windows or Office version, Conga stops developing, testing, or committing to support applications on that version.

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

System RequirementMinimum Supported Version
EO.webBrowser20.2.90
Windows OS
  • Windows 10
  • Windows 8 & 8.1
  • Windows 7

X-Author supports both the 32-bit & 64-bit versions of the above operating systems.

Microsoft Office
  • The desktop version of Office 365
  • Microsoft Word 2016 or Office 2016
  • Microsoft Word 2013 or Office 2013

Where applicable, X-Author supports 32-bit and 64-bit versions of the above applications.

The above versions assume you are using Professional or Enterprise versions of Office. Home & Student or other limited versions of Office are not supported and may be incompatible with X-Author for Contracts 1.0.

X-Author for Contracts 1.0 does not support Microsoft Word 2007.

  • Use the latest Microsoft Office suite for the best performance.
  • For some Playbook features to work, you must install Microsoft Word OS build 17134.228 update. This update is a part of the Windows 1803 build.
Microsoft .NET

Microsoft .NET Framework 4.5 or higher

Microsoft VSTOMicrosoft Visual Studio 2010 Tools for Office Runtime
Microsoft Office PIAMicrosoft Office 2010 Primary Interop Assemblies
SalesforceUnlimited, Enterprise, and Developer product editions

Upgrade Notes

If you are upgrading X-Author for Contracts 1.0 from Winter 2019 (10.0.1125.1903), you must uninstall X-Author for Contracts 1.0 and install the latest version. For more information on installation, see Installing X-Author Contracts in X-Author for Contracts for Users.

New Features

The following features are new to X-Author for Contracts 1.0  in this release.

Internal Review Using Office 365

This feature allows the internal reviewer to use X-Author for Contracts to review a document initiated from CLM using Office 365. This option also allows the contract administrator to make a final review and check in the document. For more information, see Internal Review using O365.

External Review Using Office 365

This feature allows the external reviewer to review a document initiated from CLM using Office 365. The document can be reviewed and edited online. For more information, see External Review using Office 365.

Enhancements

There are no enhancements in this release. 

Fixed Issues

The following table lists the issue fixed in this release.

Case Number

Conga Internal ID

Description

NAXA-4249Every time a user encounters a "Cannot insert a clause within a clause " error message, the user's current position is logged. 

Known Issues

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

Conga Internal IDDescription
XA-4094When you mark a clause in the template and swap that clause with the playbook clause in the agreement document, the delete entry is not created in the Agreement Clause Related list. If you add any comments to the Playbook clause during swapping, the comemntchangeonly entry is not created in the Agreement Clause Related list.
XA-3859When you review the import result after Intelligent Import, X-Author for Contracts incorrectly marks the text around fields. 
XA-3236When you check in an agreement document without changing the value of any smart field, the message prompt does not appear.
XA-2856IDE highlighting on PDF is done by IDE itself, and X-Author Contracts highlights based on approximation by various algorithms. These discrepancies can appear when IDE uses OCR to extract fields and clauses. 
XA-2793When you delete an updatable or read-only field and then click Preview Reconcile, you can see the deleted field on the reconciliation page.
XA-2743When you delete a smart field that occurs multiple times in the document, the smart fields are not correctly re-indexed in the Control Panel.
XAO-87If you have enabled Salesforce Files in your Contract Management org and you launch X-Author Outlook, connect to your org, and click Send for Review, you see an error.
XA-2580For a template with versioning enabled, the search result in playbook shows clauses that do not match the agreement type of the template.
XA-2574When versioning is enabled, different check-out features output different versions for a cloned template. When you check out a cloned template by going to Check out > Currently opened document, the template takes the version of the parent template, but if you check out a template using the Check-out search, X-Author Contracts creates the template from version 1.000.
XA-2570For template versioning-enabled orgs, when you insert the main and inline clause in a template and check it in after performing Refresh Clause, the Needs Publishing checkbox is not cleared for the header clause record.
XA-2568For versioning-enabled orgs when you change the clause content and check it in, X-Author does not display a message about affected dependent clauses or templates.
XA-2565For versioning enabled migrated templates, the Refresh document action doesn't update the new nested clause content in a template document. This occurs when you change a nested clause contained in a template document and check in the template document without first publishing the clause.
XA-2564When you change a clause in a migrated template document with versioning enabled and check in the template, X-Author Contracts does not display any acknowledgment message.
XA-2561X-Author does not reflect changes in migrated templates when templates are migrated using X-Author Migration Manager from the source org to the destination org and the destination org already contains those template records.
XA-2560Template versioning does not increment the template document version value when checking in an existing template after making changes to it. This occurs when a template is migrated from the source org to the destination org that already contains that template record.
XA-2559When you open a recently migrated template document in X-Author Contracts and click Check Out > Currently opened document, you receive an exception error and are logged out of X-Author Contracts. This occurs when you migrate a template from a template versioning enabled org to a new org, download the attachment from the template record and open it in X-Author Contracts.
XA-2509When you compare two agreement documents containing date fields - both in text and in table cells - and then accept or reject changes in the document, the date picker in some of the date fields is lost.
XA-2307When you perform an Update from Salesforce action on a generated agreement document that does not have values for the first column of the repeating table, X-Author for Contracts shows a blank screen.
XA-2260After changing the content of a marked clause and viewing it in the control panel by clicking Show Changes, X-Author for Contracts removes one character from the clause in the changes screen.

DOC ID: XAC1.0SPR20PRN20220406