Composer for Advantage Platform 202609.2.0 Release Notes
In these release notes, you can find enhancements and fixed and known issues for the Composer 202609.2.0 release. For documentation updates, see What's New in Composer 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 Composer in this release.
Salesforce Solutions Data Synchronization to Composer Solution Store
Synchronize Salesforce Solutions data to Composer Solution storage, enabling transfer and integration of solution records between systems. The feature supports migration of new and updated solutions, assigns new Solution IDs for new migrations, and retains existing Solution IDs for updates, with error handling for unresolved parameters and duplicate detection.
SalesforceOAuth Authentication Support for Ingress and Merge APIs
All Ingress APIs and downstream Merge API paths now support the SalesforceOAuth authentication schema in addition to the existing BearerV2 flow. This update enables both Conga Platform users and Salesforce-only users to authenticate and access Merge API functionality—without requiring a Conga Org ID for Salesforce-only scenarios—while maintaining backward compatibility and preserving existing error handling and activity logging. The authentication mechanism now decouples Conga Org ID requirements, allowing seamless integration for users authenticated via Salesforce OAuth.
API: Publish Button Naming Collision Handling
The POST /v1/Solution/[id]/publish API applies hybrid collision handling for Salesforce button developer names derived from solution names. If a short name (? 40 characters) collides, the API returns a 409 error; for truncated long-name collisions, a numeric suffix is auto-appended to keep the name unique within 40 characters, with up to 100 attempts before returning a 409 error. The final button name is saved in ButtonLinkApiName and reused for future updates.
Structured Error Propagation for SharePointSteward Delivery Service
The SharePointSteward delivery service now propagates structured error details using the shared DeliveryServiceError property on response contracts, enabling programmatic inspection of HTTP status codes, error phases, retryability, and sanitized error messages. All SharePoint-specific exceptions are handled and logged with appropriate severity, and sensitive information is scrubbed from error messages. This update supports more reliable error reporting and diagnostics for integration and implementation teams.
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 |
|---|---|
| COREAPPS-19835 | ColumnHide feature does not work with Conga Batch solutions. |
| COREAPPS-19754 | Conga Composer authentication expires after approximately 30 days and automatic reauthorization. |
| COREAPPS-19138 | Scheduled Batch sessions for Conga Invoice fail to execute. |
| COREAPPS-19063 | The DS7Preview parameter is not working when used in combination with the FieldDataSource parameter. |
| COREAPPS-18961 | Cross-Site Scripting (XSS) found vulnerabilities on VisualForce pages. |
| COREAPPS-18772 | Composer integrated with Sign encounters an error message when launched via the Salesforce object Work Order: “There was an issue processing the Composer request” |
| COREAPPS-18688 | After the Feb '26 Composer Salesforce package update to support API v.65, you still cannot see the Account Plan object on the Create New (Guided) experience when creating a Conga Solution. |
DOC ID: CMPRLP202609.2.0RN20261020