Composer for Salesforce June '26 Release Notes
In these release notes, you can find packages, requirements, enhancements, and fixed and known issues for the Composer June '26 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.
For training resources and feature overviews, visit the Conga Learning Center on Conga Community.
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.
Enhancements
The following enhancements are new to Composer in this release.
PKCE-Based OAuth Flow for Composer Package
Salesforce is enforcing Proof Key for Code Exchange (PKCE) and Refresh Token Rotation (RTR) for all OAuth-enabled applications. To comply, the Conga Composer OAuth architecture has been updated. Version 8.298 is also compatible with the Salesforce Summer '26 release.
On June 13, the package will be auto-pushed to your sandbox and production orgs. The running user will be prompted to "Allow" the new reduced OAuth scopes, after which all existing solutions will continue to work as normal. For customers currently blocking pop ups, we recommend you update your Connect App settings outline in documentation here or under the Configure Composer Connected App documentation. We also recommend you confirm your refresh tokens are still valid.
- Note: Customers blocking Composer NA for Salesforce, Composer EU for Salesforce, Composer AP for Salesforce Connected Apps will lose access once their tokens expire. Please allow these Connected Apps to continue using Composer as intended.
- Known Issue: Composer SF1 mobile solutions will temporarily be prevented from generating documents. On June 13, a backend fix will be applied to resume all SF1 mobile solutions.
If your org doesn't receive the auto-push on June 13, please manually install the package by June 20. Salesforce will enforce these changes on June 21. Failure to install will result in your Conga Lightning Component solutions to fail.
- Exclusion list customers: Please manually pull and install the new package by June 20.
If you have technical questions, create a technical support case.
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 |
|---|---|---|
| 00968030,00967977,00968054,00968078 | COREAPPS-18940 | Non-admin users encounter an internal server error when attempting to generate documents or send emails via Conga Invoice Generation, despite having the expected permissions and configurations applied. |
| 00955661, 00956009 | COREAPPS-18094 | When using a lightning component Composer button and uploading a local template, the user encounters the error ‘There was an error processing the local template’ |
| 00954720 | COREAPPS-17981 | Bullet points in proposal documents fail to render correctly when the "Symbol" font is used in templates on Composer for Platform. Workaround: This issue does not occur when the font is changed to "Arial". |
| 00952933 | COREAPPS-17912 | Emails sent via the Composer dialog box default to the primary contact on the Quote record, even when a different email address is specified in the 'To' field before sending. |
Known Issues
The following unresolved issues are known to Conga at the time of this release.
| Conga Internal ID | Description |
|---|---|
| COREAPPS-19138 | Scheduled Batch sessions for Conga Invoice fail to execute. |
| COREAPPS-18324 | When using PlatformComposer=1 in Conga Composer with Salesforce data, merge fields referencing inner fields on the Owner lookup (eg FullName field on User) do not populate in the generated document - despite the fields being available in Template Builder & View Data Workbook |
| COREAPPS-17938 | When using the DS7=17 or DocuSignTag=1 parameters, DocuSign status values fail to update in the Salesforce environment. This issue is not encountered when using DS7=7. |
| COREAPPS-5755 | Users are not receiving the Trigger Alert Notification email when they have exceeded their daily limits of Trigger events. |
DOC ID: CMPJUN26RN20260611