In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the CLM February '23 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.


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 Upgrade Program.

PackageLatest Certified Version NameLatest Certified Version Number
Conga Base Library (New)4.0.243


Conga Contract Lifecycle Management (New)



Conga Content Integration 8.1.00208.20

Conga DocuSign API 

(Required if you are using DocuSign)


Conga CLM DocuSign Integration 

(Required if you are using DocuSign)


Adobe Sign 

(Required if you are using Adobe Sign)


Conga CLM Adobe Sign Integration 

(Required if you are using Adobe Sign)


CongaSign CLM Integration 

(Required if you are using Conga Sign)

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.

Send Documents for Mixed Review using Office 365

You can send agreement documents for review to stakeholders in and out of your organization. You can also initiate a review cycle for mixed review that consists of both internal and external reviewers. On the review cycle page, you can differentiate the internal, external, and mixed reviews with the tags (O365 Internal Review, O365 External Review, and Office 365 Review). For more information, see Sending an Agreement Document for Collaborative Review Using Office 365 Review.

Use SharePoint Site for Office 365 Review

An administrator can create a Microsoft SharePoint site to apply security and give access to only selected stakeholders when users send Office 365 documents for internal, external, or mixed review. In the Office 365 Settings, you can use the SharePoint Site field to add Microsoft SharePoint Site. For more information, see Configuring Office 365 Settings.


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

Impact of Salesforce Org’s Hostnames Changes on CLM

To support the enhanced domains within Salesforce, Salesforce has changed the base domain URL of the sandboxes. Hence, you need to update the Instance URL comply system property with the new URL. For example, the existing URL: and the new URL: You must also ensure that Use enhanced domains and Redirect previous My Domain URLs to your current My Domain checkboxes are unselected in the My Domain Settings. For more information, see Comply System Properties.

Control Document Activation

You can configure the APTS_ActivateDocumentsSelectAll admin entry to have all documents selected or unselected during activation. You can also configure the APTS_ActivateDocumentsSelectable to allow users to select or unselect documents during activation. You can configure the APTS_ActivateDocumentsPublishAll admin entry to turn on or off Publish toggle during activation. For more information, see Admin Entries. The following table describes the impact of APTS_ActivateDocumentsSelectAll, APTS_ActivateDocumentsSelectable, and APTS_ActivateDocumentsPublishAll admin entries on the activation page.




Documents are selected?

Select or unselect documents?

Publish toggle for documents?

FalseFalseTrueNo NoOff

Import Offline Conga Generated Documents without Metadata

When you import an offline Conga document that was generated from an existing agreement into a new agreement, the existing metadata is removed and the metadata of the new agreement is added. For more information, see Importing an Offline Document.

Increase in Character Limit 

The RuntimeHelpText__c field in the WizardInputControl2__c object is introduced to increase the character limit from 255 to 510 characters for the help text on the input field in a wizard. 

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

Office365Review__cA formula field for Office 365 reviewUserNew


SharePointSite__cA field for configuring a site for office 365 reviewUserNew

RuntimeHelpText__c A field to store help text of a wizard fieldUserNew

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

The review cycle does not complete when a user reviews the document in a word processor other than MS Word.

Resolution info: When a contract administrator tries to end the review by uploading a document that was reviewed in a word processor other than MS Word, the contract administrator will receive an email notification to upload the correct document and the review cycle stays in progress.


Special characters (< , > , \\ , /) are restricted to use in the agreement name.

Resolution info: You can use special characters (< , > , \\ , /) in the agreement name.


An activity history entry is not added after sending an agreement document for Office 365 review.

Known Issues 

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

Conga Internal IDDescription
CLM-8215Activity history is not recorded after sending documents for Conga Sign signatures.

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.