Packages

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.

System Requirements and Supported Platforms

For requirements and recommendations to consider before installing the Conga product suite, see the System Requirements and Supported Platforms Matrix

New Features and Enhancements

The following features are new to CLM in this release.

Contract managers can configure in-app notifications or email notifications to help assignees stay on top of upcoming obligations. They can configure notifications to be triggered daily, weekly, or monthly based on the obligation due date. For more information, see “Setting Up Reminders for Obligations” in CLM for Salesforce users' guide.

Contract managers can change the assignee of an obligation to transfer the responsibility to another assignee. For more information, see “Editing an Agreement Obligation” in CLM for Salesforce user’s guide.

Contract managers can now link obligations directly to specific agreement milestones, allowing improved tracking of obligations in the context of key agreement events and eliminating the need for manual entry. For example, auto-populate the agreement start date value into the obligation's start date. The required field mapping can be configured in the APTS_ComplyConfig admin entry. At the time of document generation, the value will be auto-populated in the obligation record during generation. For more information, see APTS_ComplyConfig under Admin Entries in CLM for Salesforce administrators' guide.

Contract managers can now upload supporting documents and templates directly to obligation records, helping streamline obligation fulfillment. For instance, if an obligation requires compliance with environmental regulations, the contract manager can attach required documents, such as a formatted emission report, under the Files section or the Notes & Attachments section in the Related tab of the obligation record. For more information, see “Uploading Documents for Agreement Obligation” in CLM for Salesforce user’s guide.

After generating agreements, the <SortOrder> element in APTS_ComplyConfig correctly sorts the agreement line items in descending order.

Administrators can configure APTS_DefaultCurrentUserforReview_<ActionName> to automatically set the current user as the default reviewer when sending documents for simple review, parallel review, Microsoft 365 reviews (internal, external, or mixed), or Google Docs review. For more information, see the “APTS_DefaultCurrentUserforReview_<ActionName>” topic in the CLM for Salesforce administrator guide.

When an administrator enables the APTS_DefaultCurrentUserforReview_<ActionName> admin property, the current user is automatically included as a reviewer when the user sends a document for simple review, parallel review, Microsoft 365 reviews (internal, external, or mixed), or Google Docs review. For more information, see the “Sending an Agreement Document for Review”, “Sending an Agreement Document for Parallel Review”, and “Sending an Agreement Document for Collaborative Review Using Microsoft 365 Review” topics in the CLM for Salesforce user guide.

Contract managers can view obligations extracted from third-party paper agreements using the Discovery AI for Advantage Platform, in the Agreement Obligations section of the agreement’s Related tab in Salesforce. For more information, see “Viewing Agreement Obligations” under Agreement Obligations section in the CLM for Salesforce user’s guide.

Contract managers can preconfigure a default list of recipients for agreements, including the Signer Type and Routing Order for each recipient. The default recipients list is configured in the CongaSign Default Recipients section in the Related tab. When the agreement is sent for eSignature using Conga Sign, this predefined recipient list is automatically displayed, reducing manual input. The user can change the default recipients list at the time of sending the agreement for signature. For more information, see “Configuring CongaSign Default Recipients” in in CLM for Salesforce user’s guide.

Users can now regenerate large documents using the Regenerate > Submit flow without errors. Previously, this only worked with Generate > Submit. Now, both options support asynchronous processing for better performance. For more information, see the “Generating an Agreement Document using a Microsoft Word template” topic in the CLM for Salesforce user guide.

Administrators can set the APTS_HideGenerateAction admin property to true to hide the Generate button for generating large documents and use the Submit button instead.For example, if the number of Agreement Line Items exceeds the limit set in the Large Doc Threshold comply system property, or if any custom object listed in the APTS_LargeDocSObjects admin property exceeds its threshold, the system automatically hides the Generate button. For more information, see the “APTS_HideGenerateAction” topic in the CLM for Salesforce administrator guide

When an administrator enables the APTS_HideGenerateAction admin property, the system hides the Generate button while generating large documents, and users can use the Submit button instead. For more information, see the “Generating an Agreement Document using a Microsoft Word template” topic in the CLM for Salesforce user guide.

Data Model Changes

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

Fixed Issues

There are no fixed issues in this release.

Known Issues

There are no known issues in this release.

DOC ID: CLMJUN25RN20250603