This Release Notes contain the following information about X-Author Contracts Spring 2020 Patch 7 Release on Salesforce.

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
  • 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

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.5.819.2001 | 11.5.819

Conga Contract Lifecycle Management (New)

11.0.0519.11 | 11.519.11

Before installing or upgrading Apttus managed packages, you must review the dependency matrix for each managed package. You can refer to the package dependency matrix at Packages Dependency Matrix

System Requirements and Supported Platforms

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

  • You cannot use a Mac OS X operating system with X-Author Contracts; 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 Apttus X-Author Contracts can only be used in a Windows desktop environment.

  • New features and technologies are continuously deployed in new releases by Apttus X-Author Contracts, and they are supported by Apttus 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 Apttus 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 Contracts.

System RequirementMinimum Supported Version
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

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 Contracts.

Apttus no longer supports Microsoft Word 2007 with X-Author Contracts.

  • Apttus recommends using the latest Microsoft Office Suite for best performance.
  • For some Playbook features to work, you must install Microsoft Word OS Build 17134.228 update. This update is a part of 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 in the X-Author Contracts User Guide.

New Features

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

Enhancements

There are no enhancements in this release.

Data Model Changes

This release does not have any data model changes for X-Author Contracts.

Resolved Issues

The following table lists the issues resolved in this release.

Case NumberApttus Internal IDDescription
00104653XA-4018

A user encountered an error during login to X-Author Contracts when the user had a single sign-on login with Azure Active Directory as an identity provider and Conditional Access Policy was enabled. The user observed this behavior when using the EO browser.

Resolution: If you are unable to login to X-Author Contracts using single sign-on along with the below settings:

  • Azure Active Directory as an identity provider
  • EO browser
  • Conditional Access Policy is enabled

you must use Internet Explorer browser and add <UseMicrosoftWebBrowserControlForLogin>True</UseMicrosoftWebBrowserControlForLogin> configuration in X-Author Contracts.config file.

NAXA-4007

PDF security did not apply to documents that were checked-in as Final-to be signed with Create PDF attachment option selected. A user with permissions other than System Administrator observed this behavior.

Resolution: If you are using the Apttus Contract Management package version prior to 11.546 version, the system administrator must assign Apttus.Comply System Properties to your user profile to enable PDF security feature for your profile. If you are using the Apttus Contract Management package version 11.546 or later version, the PDF security feature is enabled for all user profiles by default.

00103079XA-4005When a user inserted clauses from Playbook into a template that had paragraph number formatting, the number formatting for clauses was not retained during check-in of the template.
00104256XA-3999When a user modified a clause in an agreement document and checked-in the document with Final-to be signed, Reconcile Document and Create PDF Attachment options selected, the final clause entry did not contain the modified text in Agreement Clauses related list. The user observed this behavior when the clause was created using the mark as clause functionality in the template.
00101935XA-3953When a user added Conditional Segment or merge fields in the header and footer section of a template by applying section break, the user encountered an Invalid AptObject exception while generating an agreement document using that template.
NAXA-3900

When a user generated an agreement document using a template that had template level locale formatting, but no clause level locale formatting, the template level locale formatting did not apply to the Number and Currency fields in the clause.

Resolution: When the locale formatting is not defined for a clause, the clause inherits the template level locale formatting in the generated agreement document.

Known Issues

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

Apttus Internal IDIssue
XA-3859When you review 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 based on approximation by various algorithm process. As IDE uses OCR to extract field and clauses, such 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 template 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, 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-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 which 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 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: XACSFSPR20P7RN20200821