CLM for Salesforce October '25 Release Notes
In these release notes, you can find packages, requirements, new features and enhancements, and fixed and known issues for the CLM October '25 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.
To access the learning path, including overviews and demonstrations of this release’s updated features and enhancements, visit the Conga Learning Center.
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.
You can register your org for 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 ensures that all the Conga published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Upgrade Program.
| Package | Latest Certified Version | |
|---|---|---|
| Name | Number | |
Conga Base Library (Changed) | 6.2.285 | 6.285 |
Conga Contract Lifecycle Management (Changed) | 16.2.799 | 16.799 |
Conga Content Integration | 8.1.0020 | 8.20 |
Conga DocuSign API (Required if you are using DocuSign) (Changed) | 8.1.142 | 8.142.28 |
Conga CLM DocuSign Integration (Required if you are using DocuSign) | 5.1.50 | 5.50.9 |
Adobe Sign (Required if you are using Adobe Sign) (Changed) | 25.6 | 25.6 |
Conga CLM Adobe Sign Integration (Required if you are using Adobe Sign) (Changed) | 10.1.73 | 10.73.10 |
CongaSign CLM Integration (Required if you are using Conga Sign) | 3.1.23 | 3.23 |
Conga For Salesforce (Required if you sync data between Salesforce and Conga Platform) (Changed) | 2.1.12 | 2.12 |
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.
October '25 Upgrade Impact
The CLM application now uses the JWT (JSON Web Token) flow for authentication. This change enhances application security and ensures more secure authentication management.
- Click Conga SF Connected App in Installed Connected Apps and click
.
Conga SF Connected App is added to Enabled Connected Apps list.
New Features and Enhancements
The following features are new to CLM in this release.
Audit Logs – Standardized Project Name
The Project Name field sent to audit logs is now standardized to ensure consistent identification, tracking, and reporting across all records. For more information, see Logs.
Agreement Obligation Fulfilment
Users can manage and track the completion of obligations from the Obligation Fulfillment page. Assignees can submit obligations for fulfillment by providing necessary information, which then triggers a review process. Reviewers can accept or reject the submitted fulfillment based on its completeness and accuracy. At any point of time, contract managers will be able to waive an obligation fulfilment. For more information, see Obligation Fulfillment in CLM for Salesforce user’s guide.
Activate Obligations
Upon contract activation, all associated obligations are automatically activated and corresponding obligation fulfillment records are created with a status of Pending Fulfilment. Editing, adding, or deleting obligations is restricted once the contract is activated. For more example, see Activating an Agreement in CLM for Salesforce user’s guide.
Enhancements to Parallel Review Submission Failure Notification Email Template
The notification email template, now includes the agreement name and agreement number. Administrators can customize the template to add a link to the agreement and insert custom merge fields. When the email is sent, all merge fields are populated with the correct agreement details. For more information, see Submitting Reviewed Documents by Email under Sending an Agreement Document for Parallel Review in CLM for Salesforce user’s guide.
Data Model Changes
The following objects and fields are introduced to or changed in the system or data model in this release.
| Object | Field | Description | System/User | New/Changed |
|---|---|---|---|---|
| AgreementObligationFulfillment__c | To store agreement obligation fulfillment | System | New | |
| AgreementObligation__c | To store agreement obligation | System | New | |
| AssigneeContact__c | To store agreement obligation assignee contact | System | New | |
| DueDate__c | To store agreement obligation fulfillment due date | System | New | |
| FulfillmentDate__c | To store agreement obligation fulfillment date | System | New | |
| Status__c | To store agreement obligation fulfillment status | System | New | |
| Reviewer__c | To store agreement obligation fulfillment reviewer | System | New | |
| ReviewerContact__c | To store agreement obligation fulfillment reviewer contact | System | New | |
| Assignee__c | To store agreement obligation fulfillment assignee | System | New |
Fixed Issues
There are no fixed issues in this release.
Known Issues
There are no known issues in this release.
DOC ID: CLMOCT25RN20250925
