Download PDF
Download page Conga CLM for Salesforce June '24 Release Notes.
Conga CLM for Salesforce June '24 Release Notes
In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the CLM June '24 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 Push Upgrade.
| Package | Latest Certified Version | |
|---|---|---|
| Name | Number | |
Conga Base Library (New) | 5.1.266 | 5.266 |
Conga Contract Lifecycle Management (New) | 15.1.750 | 15.750 |
Conga Content Integration | 8.1.0020 | 8.20 |
Conga DocuSign API (Required if you are using DocuSign) | 8.1.142 | 8.142.18 |
Conga CLM DocuSign Integration (Required if you are using DocuSign) | 5.1.50 | 5.50.7 |
Adobe Sign (Required if you are using Adobe Sign) (New) | 24.37 | 24.37 |
Conga CLM Adobe Sign Integration (Required if you are using Adobe Sign) | 10.1.73 | 10.73.3 |
CongaSign CLM Integration (Required if you are using Conga Sign) | 1.2.16 | 1.16 |
Conga For Salesforce (Required if you sync data between Salesforce and Conga Platform) | 1.0.5 | 1.5 |
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
In this release, Conga CLM offers the following new features and enhancements.
CLM API Support
Support of CLM API (afterImportOfflineDocsAsync) is required to create an agreement and import offline agreements in Conga for Google Docs.
Disable the Auto-Checkout of Contracts
The Conga Contract Lifecycle Management.Apttus.XA_DisableAutoCheckout custom permission, when set to true, does not automatically check out contracts.
For more information, see Custom Permissions.
Allow Accept/Reject from Third Party during Microsoft 365 Review
Administrators can allow or disallow external reviewers to accept or reject changes in the document received for review through Send for Office 365 Review. For more information, see Setting Up Microsoft 365 Review and Sending an Agreement Document for Collaborative Review Using Microsoft 365 Review.
Improved Agreement Creation User Experience
The user interface (UI) for new agreement creation is modified for a look and feel similar to the Salesforce Lightning UI.
Improved Agreement Management User Experience
For the following actions, the user interfaces are modified for a look and feel similar to the Salesforce Lightning UI:
- Amend agreement
- Clone agreement
- Renew agreement
- Cancel agreement
- Expire agreement
- Terminate agreement
Filter with Template Unique Name
You can search for templates using a template name or the template's unique name. If you search by a template name, the system searches the templates based on their names and displays relevant results. If you search by a template's unique name, the system searches the templates based on their unique names and displays relevant results. For more information, see Finalizing an Agreement, Sending an Agreement Document for Review, and Sending an Agreement Document for Parallel Review.
Status and Status Category of Child Agreement (Amended or Renewed)
You can configure the APTS_StatusCategoriesToInclude admin entry to update any child agreement's (amended or renewed) status and status category to Expired or Terminated when the parent agreement status is expired or terminated.
You can configure the APTS_StatusCategoriesToExclude admin entry to block updating any child agreement's (amended or renewed) status and status category to Expired or Terminated when the parent agreement is expired or terminated. For more information, see Admin Entries, Terminating an Agreement, and Expiring an Agreement.
Viewing the Document from the Document Version Related List
After checking the Google Docs template in, you can view the document by clicking the View link in the Document Version related list. For more information, see Generating an Agreement.
Naming Convention for Amended, Cloned, or Renewed Agreements
Administrators can configure a default naming convention for agreements generated on amending, cloning or renewing agreements. They can override the default naming convention by configuring action-specific admin entries. For more information, see APTS_AgreementNAme_Default, APTS_AgreementName_Amend, APTS_AgreementName_Clone, APTS_AgreementName_Renew in Admin Entries.
Agreements Related to Amended or Renewed Agreements
You can view amended & renewed agreements and agreements related to them from an Account’s Agreement Hierarchy. For more information, see Viewing Account’s Agreement Hierarchy.
Related Agreements in Account’s Agreement Hierarchy
You can view agreements related to the amended or renewed agreements displayed in Amendment and Renewals section in the parent agreement's hierarchy. For more information, see Viewing Agreement Hierarchy.
User.ReadBasic.All Graph API Permission
As an administrator, you can configure delegated permission flow with User.ReadBasic.All Graph API permission to allow Azure App to read a basic set of profile properties of other users in your organization on behalf of the signed-in user.
Agreement Actions after Generating an Agreement
After checking the Google Docs template in and generating an agreement, you can:
- Send the agreement for manual signature
- Send the agreement for eSignature
- Activate the agreement
- Amend, renew, or clone the agreement
For more information, see Finalizing an Agreement, Activating an Agreement, and Managing Agreement Lifecycle Post-Activation
Generating an Agreement
After checking a Google Docs template in, you can generate and submit an agreement. For more information, see Generating an Agreement.
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 |
|---|---|---|---|---|
| Office365Settings__c.object | Changed | |||
| AllowAcceptRejectFromThirdParty__c | Added to allow external reviewer to accept or reject changes | Changed |
Fixed Issues
The following issues are fixed in this release. If any actions are required, they will be listed in this table.
| Case Number | Conga Internal ID | Description |
|---|---|---|
| 00887936 | CONTRACTS-20061 | On multiple occurrences, the Cross-site Request Forgery (CSRF) is being performed on the Wizard page. This allows an attacker to force users to perform actions they would not intend to. Workaround: Customers using the Wizard.page in the formula field or hyperlink can update per the Salesforce documentation https://help.salesforce.com/s/articleView?id=000383876&type=1 |
| 00881623 | CONTRACTS-19336 | The account search field on agreement records does not populate correctly when creating an agreement. |
Known Issues
There are no known issues in this release.