These Release Notes contain the following information about X-Author for Contracts 1.0 (previously known as X-Author Contracts) Spring20.10.14 Release.

For more information on new features, enhancements, and document improvements, refer to What's New in X-Author for Contracts 1.0 Documentation.

  • 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
  • Data Model Changes: Lists changes to the data model
  • Fixed Issues: Lists customer-reported issues that are fixed in this release or known issues resolved from previous releases
  • Known Issues: Lists known issues that are applicable in this release

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 dependent packages are required to upgrade to this release to utilize all the new features of 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.

Product

Latest Certified Version

Version Name | Version Number

X-Author Contracts (New)

11.23.1012.2001 | 11.23.1012

Conga Contract Lifecycle Management

12.0.0630 | 12.630

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

X-Author for Contracts 1.0 is a Microsoft Word Add-In that is accessed via Microsoft Word application on your Windows machine. For the X-Author for Contracts 1.0 Add-In to work, the Conga Contract Lifecycle Management package must be installed in your Salesforce Org. This is required so that the various dialog boxes available in X-Author for Contracts 1.0 can display the correct fields. Once this is done by your system administrator, you will be able to install the X-Author for Contracts 1.0 Add-In and begin using it.

  • You cannot use a Mac OS X operating system with X-Author for Contracts 1.0; however, it can be used with a Mac running a Windows Virtual Machine in a Citrix environment.

  • Microsoft’s Office 365 Online or Cloud applications do not support plugins; therefore, the X-Author for Contracts 1.0 can only be used in a Windows desktop environment.

  • New features and technologies are continuously deployed in new releases by X-Author for Contracts 1.0, and they are supported by Conga, where the associated Microsoft OS and/or Microsoft Office versions are also still supported by Microsoft. As Microsoft ends its support for any OS and/or Office version, subsequent new Conga releases will no longer be developed, tested, or committed to support the application on any Microsoft OS and/or Office version which is no longer supported by Microsoft.

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

Microsoft Word 2010 or Office 2010

*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 or may not prove to be compatible with X-Author for Contracts 1.0.

Microsoft Word 2007 with X-Author for Contracts 1.0 is not supported.

  • 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) to any latest version, you need to uninstall X-Author for Contracts 1.0 and install the latest version. For more information on installation, see Installing X-Author Contracts

New Features

There are no new features in this release. Keep checking the Conga Documentation Portal for new updates.

Enhancements

There are no new enhancements in this release.

Data Model Changes

There are no data model changes in this release.

Fixed Issues

The following table lists the issues fixed in this release. If any actions are required, they will be listed in this table.

Case NumberConga Internal IDDescription
00770630XA-4202

After you delete clauses with keystroke (using Backspace or Delete button), the clauses are not available for reconciliation and the clause deletion does not reflect in the Agreement Clauses. 

Known Issues

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


Conga Internal ID

Description

XA-4189

Templates created from X-Author for Contracts 2.0 with marked clauses and used in X-Author for Contracts 1.0, the following issues occur while reconciling:

  • If you mark a clause in X-Author for Contracts 2.0 and add some exceptions during the marking process, then delete the marked clause from X-Author for Contracts 1.0, the application displays an error while reconciling, but the check-in will be successful.

  • If you delete the marked clause using the delete key on your keyboard and then check in the document,
    • The deleted action logged under the Agreement Clauses related list interchanges the content in the Previous Text and Text columns.
    • The previous and primordial clause numbers are not getting populated.
  • When you unlock the read-only clause for modification and check in the document, the modified action for the read-only clause logged under the Agreement Clauses related list does not display the primordial and previous clause numbers.
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 commentchangeonly entry is not created in the Agreement Clause Related list.
XA-3859When you review the import result after Intelligent Import, X-Author 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 are based on approximation by various algorithm processes. As IDE uses OCR to extract fields and clauses, such a difference exists.
XA-2793When you delete an Updatable or ReadOnly 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 the Salesforce Files system 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 template versioning enabled, the search result in Playbook shows clauses that do not match the agreement type of the template.
XA-2574For versioning enabled templates the Check-out feature gives different versioning output for the 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 org, when you change the clause content and check it in, X-Author does not display a message about the affected dependent clauses or templates.
XA-2565For versioning enabled migrated template, 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-2564X-Author Contracts does not display any acknowledgment message when you change a clause in a migrated template document with versioning enabled and checked in the template.
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-2560The template 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, containing 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 Update from Salesforce action on a generated agreement document that does not have values for the first column of the repeating table, X-Author 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 Contracts removes one character from the clause in the changes screen.

DOC ID: XAC1.0SPR20PRN20211014