In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the CLM May '22 release. For documentation updates, see What's New in CLM Documentation.

This documentation may describe optional features for which you have not purchased a license; therefore your solution or implementation may differ from what is described here. Contact your Customer Success Manager (CSM) or Account Executive (AE) to discuss your specific features and licensing.

All Conga customers have FREE access to getting started content and release training in the Conga Learning Center. To take your training further, ensure your organization has access to the Conga Learning Pass, which is a training subscription service. Click here to learn more.


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.

You can register your org for the Conga Push Upgrade. Conga Push Upgrade is an automated tool that upgrades packages available in your Salesforce org (Production or Sandbox) to the latest versions. In addition, it also ensures all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Push Upgrade.

PackageLatest Certified Version (Name | Number)
Conga Base Library (New)

3.0.232 | 3.232

Conga Contract Lifecycle Management (New)

13.0.669 | 13.669
Conga Content Integration 8.1.0020 | 8.20

Conga DocuSign API (New)

(Required if you are using DocuSign)

8.0.117 | 8.117

Conga CLM DocuSign Integration (New)

(Required if you are using DocuSign) | 4.48.1

Adobe Sign (New)

(Required if you are using Adobe Sign)

23.14.3 | 23.14.3

Conga CLM Adobe Sign Integration (New)

(Required if you are using Adobe Sign) | 9.69.1

Conga Sign Integration 

(Required if you are using Conga Sign)

1.2.6 | 1.6

For more information on installing CLM managed packages, see Installing Conga CLM. For more information on upgrading CLM managed packages, see Upgrading Conga CLM.

If you use CLM in Salesforce Lightning, you must enable the Enable Files Comply System Property.

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

The following features are new to Conga CLM in this release.

Integrate CLM with Conga Contract Intelligence

Conga Contract Intelligence is an artificial intelligence tool that extracts unstructured text from agreements and organizes it into structured data. You can obtain a Conga Contract Intelligence license from Conga and integrate it with CLM to import documents and process them. First, you must configure CLM to support the integration and then configure Contract Intelligence for CLM. After you integrate CLM with Conga Contracts Intelligence, you can import, extract, review, and approve documents. For more information, see Setting Up Contract Intelligence for CLM and Contract Intelligence for CLM.

Send an Agreement Document for Collaborative Review using Office 365 Review

You can send the agreement documents to Office 365 for collaborative review in Salesforce Lightning mode. In Office 365, you can collaboratively edit and review an agreement document with all the team members and view live changes. A review cycle is created when you send an agreement document in DOCX format for Office 365 review. All the documents opened using Office 365 have Insert Comments and Track Changes protection mode.

You can send agreement documents to both stakeholders within and outside your organization for review separately. You can create one review cycle for internal stakeholders and one for external stakeholders. On the review cycle page, you can differentiate the internal and external stakeholders' reviews with the tags (O365 Internal Review or O365 External Review). For more information, see Configuring Office 365 Settings and Sending an Agreement Document for Collaboration Review using Office 365 Review


The following enhancements are new to Conga CLM in this release.

Changes to Agreement Name

From May '22 release, you must not use special characters (< , > , \\ , /) in the agreement name to avoid errors while creating a new agreement. If you have any existing agreements with special characters (< , > , \\ , /), you must remove the special characters (< , > , \\ , /) when you amend, renew, or update the agreement to avoid errors.

Updates to Review Cycle Page

When you send documents for review using different review tools, you can see all review cycles of documents on the review cycle page with corresponding tags (Parallel Review or MS Teams or O365 Internal Review or O365 External Review). The following image shows different review cycle tags.

Moved Review Buttons on the MS Teams Review Cycle Page

You can see the End review, Cancel Review, and Add Reviewers buttons on the header of the page. For more information, see Sending an Agreement Document for Microsoft Teams Review.

Translate Picklist Values in Documents

When an administrator sets the APTS_TranslatePickValuesInDocs admin entry to true, the picklist field value gets added in the generated document. If a conditional segment is set, the condition takes both API and picklist values. You can either use API names or Values but not both.

When an administrator sets the APTS_TranslatePickValuesInDocs admin entry to false or does not add the admin entry, the API Name of the picklist gets added in the generated document by default.

For more information, see Admin Entries.

Unsubscribe from Parallel Review Emails

When the value of the APTS_SuppressAutoReviewEmails admin entry is true, users will be unsubscribed from parallel review emails (review completion, review error, and review cycle completion). For more information, see Admin Entries.

Apply Version Number to Merged Document

When the value of the APTS_AppendVersionNumberToMergedDocs admin entry is true and the Enable Document Versioning and Enable Version Control Comply System Properties are enabled, the name of the merged documents will be suffixed with a version number. For more information, see Admin Entries.

Retain Existing Header and Footer or Add Custom Header and Footer in the Merged Document

When you merge documents, you can select Retain Header and Footer to retain the header footer of the original document in the merged documents. You can select Custom Header and Footer to see Header and Footer fields and add a custom header and footer. For more information, see Merging Documents in Salesforce Lightning. 

Remove Page Breaks Between Merged Documents

When the APTS_KeepSectionBreaks admin entry is set to false, page breaks are not added between merged documents. For more information, see Admin Entries.

Data Model Changes 

The following objects and fields are introduced to or changed in the system or data model in this release.

ObjectFieldDescriptionSystem/UserNew/ Changed



URL to download the uploaded document



Stores errors from Office 365



Status type of the Office 365 review cycle



Status of the Office 365 review cycle



Review Cycle lookup



Upload URL of Office 365



File Id of the uploaded document



Sharable link to the Office 365 document to send to reviewers


Fixed Issues 

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

Case NumberConga Internal IDDescription

When you configure a required dependent picklist on the agreement object and the dependent field does not have any values for controlling field value, you encounter an error. 


You encounter an error when you create an agreement from an opportunity in the community.

Resolution info: The APTS_EnableLightningCommunity admin entry is introduced. When the APTS_EnableLightningCommunity admin entry is set to true, all users in an org are considered as Lightning Community users and are navigated to the Agreement Detail page after a user clicks New Agreement on an Opportunity. For more information, see Admin Entries.

Known Issues 

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

Conga Internal IDDescription

You encounter an error when you click in the TO field while sending a document for review using the Safari browser.

Workaround: Use Chrome or Microsoft Edge to send documents for review.

CLM-7204If a validation rule fails, the duplicate agreement is marked as transient.
CLM-6792If you see the Import Large File button in the Additional Actions section of the action panel, you must not use it to import files. This option is disabled in Spring '21 release.
CLM-5367In the Console tab, when you click Cancel, the tab does not close while sending for signatures and sending for review.
CLM-5359When you choose any value instead of the first value in the wizard lookup field in Salesforce Classic, the value resets to the first value.
CLM-5988When you use a checkbox object field in input rules condition, checked and unchecked options are not visible.

If the Set This Control Value rule is set on an input field, you cannot modify the input in the wizard.


When you open a wizard in the Classic mode with rules on a Lookup field, you encounter an error.

CLM-5367The console app tab remains open on canceling sending for signatures and review.
CLM-5207The console app displays the Generate button even after the user has generated the document.

On Partner Community portals, when you try to upload an offline agreement or check in an existing template to agreements in FX2 format from X-Author Contracts, an error message is displayed for version-aware and non-version-aware files or attachment type document.

CLM-3212The Work Order custom object is not enabled for a template object of the Pre FX2 format.
CLM-3211Agreement flow does not work for Communities in the Salesforce Lightning mode.
CLM-2730In the Salesforce One app, when a user clicks the Agreement Actions from the Action panel once, the user stays on the same page. To go to the next page, the user must click twice. This is a Salesforce limitation for embedded Visualforce pages.
CLM-2690In the Salesforce One app, clicking the lookup option does not open a new pop-up window.