Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

CLM for Salesforce February26.26.0713 Release Notes

In these release notes, you can find packages, requirements, enhancements, and fixed and known issues for the CLM February26.26.0713 release. For documentation updates, see What's New in CLM Documentation.

Note:

This documentation may describe optional enhancements 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 enhancements and licensing.

Packages

The following packages and dependencies are required to upgrade to this release and use its enhancements. These are the minimum required versions; later versions are also supported. Prerequisites for each enhancement can be found in its documentation. Packages marked (New) are new for this release.

Note:

You can register your org for the Conga Upgrade Program, an automated tool that keeps all Conga managed packages in your Salesforce org (production or sandbox) updated to the latest versions. For more information, see Registering for Conga Upgrade Program.

PackageLatest Certified Version
NameNumber
Conga Contract Lifecycle Management17.815.517.0.815.5
Conga Base Library7.288.17.0.288.1
Adobe Sign26.326.3
Conga CLM Adobe Sign Integration10.73.1410.1.73
Conga for Salesforce2.122.2.12
Conga CLM DocuSign Integration5.50.115.1.50
Conga DocuSign API8.142.328.1.142
Conga Content Integration8.208.1.0020
Conga Sign1.93Feb 2026 r2
CongaSign CLM Integration3.243.1.24

Enhancements

There are no enhancements in this release.

Fixed Issues

The following issues are fixed in this release. If any actions are required, they will be listed in this table.

Case NumberConga Internal IDDescription
NACONTRACTS-42090

The deprecated public resource Apttus__OCCResource/ webBasedRichTextEditor/index.html is vulnerable to DOM-based XSS because it uses the serverurl query parameter directly in document.write() without proper sanitization.

NACONTRACTS-41967

When users import multiple supporting documents in a single operation, the Document Type field does not consistently retain the selected custom value. Previously added documents automatically revert to Supporting Document when users add more documents before importing, even when the Supporting Document picklist value is inactive. This behavior assigns an incorrect document type during document import.

Known Issues

There are no known issues in this release.

DOC ID: CLMFEB26PRN20260713