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


Conga Contract Lifecycle Management (New)



Conga Content Integration 8.1.00208.20

Conga DocuSign API (New)

(Required if you are using DocuSign)


Conga CLM DocuSign Integration 

(Required if you are using DocuSign)


Adobe Sign (New)

(Required if you are using Adobe Sign)


Conga CLM Adobe Sign Integration (New)

(Required if you are using Adobe Sign)


CongaSign CLM Integration (New)

(Required if you are using Conga Sign)



Conga For Salesforce (New)

(Required if you sync data between Salesforce and Conga Platform)

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.


Migrating Workflow Rules to Flow

Salesforce recommends that users leverage Flows as they offer more flexibility and robust capabilities compared to Workflow Rules and Process Builders. To ensure a smooth transition from Workflow Rules and Process Builders to Flows and to prevent issues when Salesforce deprecates Workflow Rules, you must deactivate any existing Workflow Rules. After you have installed the latest CLM package in your org, Flows are created automatically. The Flows have the same functionality as Workflows. Hence, you must deactivate the following Workflows:

  • Search Field Update
  • Set Agreement Number

To deactivate workflows:

  • In Salesforce Classic, go to Setup > App Setup> Create > Workflow & Approvals > Workflow Rules > Click Deactivate
  • In Salesforce Lighting, go to Setup > Platform Tools > Process Automation > Workflow Rules > Click Deactivate.

If you had temporarily migrated Workflow Rules to Flow before installing the latest CLM package, you must delete the temporary flows.

New Features

The following feature is new to Conga CLM in this release.

Integrate with OneSpan Sign

An administrator can integrate OneSpan Sign to allow users to send documents for eSignatures using OneSpan Sign from CLM.

For more information, see Integrating with Conga CLM for Salesforce.

Enhanced Send for Signature User Interface

The Send for Signatures user interface is enhanced for a better user experience. 

For more information, see Finalizing an Agreement.

Sync Data between Salesforce and Conga Platform for CLM

An administrator must perform the following tasks to sync data from CLM for Salesforce to Conga Platform:

  • Configure a Salesforce authentication provider to log in to CLM on Conga Platform using Salesforce credentials.
  • Configure the APTS_RLPInstanceSettings admin entry.
  • Configure remote site settings.
  • Configure triggers to sync the out-of-the-box objects to CLM on Conga Platform.

For more information, see Syncing Data between Salesforce and Conga Platform for CLM.


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

Document Attachment Options for Activation Notification

When you turn on the Notify others toggle to notify other stakeholders, the documents you selected during activation are attached to the activation notification email by default. You can unselect documents that you do not want to attach to the activation notification email.

For more information, see Activating an Agreement.

Completing the Office 365 Review Cycle via Email

Administrators can enable the ApttusEndReviewByEmailO365 email service and configure the APTS_EndOffice365ReviewEmailServiceAddress admin entry to allow Office 365 document reviewers to end an Office 365 review via email. This functionality is only available through app level flow and not delegated flow. 

For more information, see Configuring Email Service for Ending an Office 365 Review by Email.

After a reviewer completes a review via email, the review cycle's status changes from In Progress to Completed. When reviewers end a review cycle through email, and they have reviews in progress in other review cycles, reviews in those other review cycles are also marked as completed. The document is then archived, preventing further edits by the reviewer. Reviewers receive a notification email confirming the review's completion once their reply to the review email is processed. To access the reviewed document, navigate to the Document Version Detail page. 

For more information, see Sending an Agreement Document for Collaborative Review Using Office 365 Review.

Removed Dependency on APTS_DefaultEmailContactName

The APTS_DefaultEmailContactName admin entry does not affect the review process.

Customize the Add More Button 

An administrator can configure the Show Add More Button During Signature comply user property, to allow users to view the Add more button while sending documents for signature to add supporting documents from their local or shared drive. If the property is not configured, the Add more button is visible to all users by default.

For more information, see Comply User Properties and Finalizing an Agreement.

Restriction for External Reviewers

When you send documents for review using Office 365, external reviewers cannot accept or reject the changes in the review document. If the reviewers open the Office 365 review documents on the desktop, the reviewers can see that the Accept and Reject options are disabled in the Review tab.

For more information, see Sending an Agreement Document for Collaborative Review Using Office 365 Review.

Email Notification for Office 365 Review

After a review cycle is completed, an email notification is sent to all the reviewers to inform them that the document review process has been completed.  

For more information, see Sending an Agreement Document for Collaborative Review Using Office 365 Review.

Add Primary Contact in the Email's To Field

When the APTS_IncludePrimaryContact admin entry is set to true, it adds the primary contact from the agreement to the To field of the email.

For more information, see Sending an Agreement Document for Review, Sending an Agreement Document for Parallel Review, Sending an Agreement Document for Collaborative Review Using Office 365 Review, Finalizing an Agreement, and 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


ShowAddMoreButtonDuringSignature__cIndicates whether users can view the Add more button while sending documents for signature UserNew

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

You cannot add reviewers to an ongoing review cycle and the status remains Not Started.

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.