Preview: Conga Advantage Platform 202603.1.0 Release Notes
In these release notes, you can find enhancements and fixed and known issues for the Conga Advantage Platform 202603.1.0 release. For documentation updates, see What's New in Conga Advantage Platform Documentation.
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 Conga Advantage Platform in this release.
Prevent Deletion of Activities with Dependent Outputs in Workflow Builder
Conga Advantage Platform now prevents you from deleting a Data Transformation (DTA) or HTTP Callout V2 activity if other activities in the same workflow use its Activity Output. When you try to delete one of these activities, the workflow builder displays a validation message listing the dependent activities. You must remove or update those dependencies before you can delete the activity.
Restore Activity Output on Workflow Resume
Conga Advantage Platform now saves Activity Output values in the workflow instance state and then restores them when the workflow resumes. This ensures that Data Transformation (DTA) variables and expressions that reference Activity Output continue to work correctly after a workflow is suspended and resumed.
Data Sync: New Support for External Client App
Conga Advantage Platform now supports Salesforce External Client Apps using the OAuth 2.0 Client Credentials Flow, enabling secure, non-interactive server-to-server integrations. For more details, see Configure OAuth 2.0 Authentication for Salesforce Data Sync.
Fixed Issues
There are no fixed issues in this release.
Known Issues
The following unresolved issues are known to Conga at the time of this release.
| Conga Internal ID | Description |
|---|---|
| PEET-2554 | The Cart Activation API may fail intermittently in some scenarios. When this occurs, cart data does not sync to the Cart database, which may prevent pricing execution and impact downstream processes. |
| EUF-6692 | When creating a proposal page for a specific record type, the system might display the wrong type, and Quote page might show the page incorrectly for that record type. |
DOC ID: RLP202603.1.0RN20260323