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

Sign for Salesforce February26.26.0511 Release Notes

In these release notes, you can find packages, requirements, enhancements, and fixed and known issues for the Sign February26.26.0511 release. For documentation updates, see What's New in Sign 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.

Enhancements

The following enhancements are new to Sign in this release.

PKCE and Refresh Token Rotation Support in CongaSign OAuth 2.0 Flow

The CongaSign backend now supports Proof Key for Code Exchange (PKCE) and Refresh Token Rotation (RTR) in the OAuth 2.0 authorization flow, including the oauth2/authorize and oauth2/token endpoints. This update enables secure authentication and persistent connections for organizations with or without the global PKCE requirement enabled in OAuth and OpenID Connect Settings, and maintains connection continuity for connected apps with RTR enabled.

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
NA COREAPPS-15209

Processing certain documents causes out-of-memory errors in document worker pods, leading to service degradation and frequent restarts.

Known Issues

The following unresolved issues are known to Conga at the time of this release.

Conga Internal IDDescription
COREAPPS-19171

The ContentDocumentId field on the Conga Sign Transaction Object has been fully deprecated after no longer being supported with the release of multiple document support. This change was necessary to comply with platform-level requirements enforced by Salesforce. If you have any flows, process builders, Apex code, reports, or other automation referencing this field, we recommend updating those references to use the ContentDocumentId field on the Conga Sign Document Object instead, which has been and continues to be fully supported. If you have questions or need assistance, please contact Conga Support.

DOC ID: CSFEB26PRN20260513