In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Conga Composer June '23 release. For documentation updates, see What's New in Composer Documentation.

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


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


Latest Certified Version Name

Latest Certified Version Number
Conga Composer 

Mount Belford

Conga Batch 


Conga Trigger 




  • The Composer Mount Belford 8.234 Package was automatically pushed out to all Sandbox environments on January 25th, 2023, and has been pushed to all Production environments on May 16th, 2023. Failure to upgrade to this version will result in Lightning Component solutions and the Document Automation Wizard becoming unavailable for customers on the Salesforce Spring '23 Release. Composer Mount Belford 8.234 is fully compatible with the Salesforce Summer '23 Release and no action is required for customers.
  • If your Production environment has not received the automatic upgrade, you can refer to our troubleshooting tips to manually update. 
  • Moving forward from May, all updates to Composer's Salesforce package are installed automatically in all accounts at the time of release. With our automatic installation of the latest Conga Composer Salesforce package on May 16th, this will remove the Conga Composer reliance on the Salesforce API versions 21.0-30.0 scheduled for deprecation with the Salesforce Summer '25 release.  

For more information on installing Composer managed packages, refer to Installing Composer Package. For more information on upgrading Composer managed packages, refer to Upgrading to the Latest Version of Composer.

System Requirements and Supported Platforms 

For information pertaining to the requirements and recommendations, you must consider before you proceed with the installation of the Conga product suite, see System Requirements and Supported Platforms Matrix.

New Features

There are no new features in this release.


The following enhancements are new in this release. 

Enhanced details for Composer API Error Messages 

The Composer Document Generation Status API will provide detailed information regarding the cause of the merge process error. For information regarding the API, see Conga Document Generation Status APIs.

Composer Activity Report includes API Usage

The Composer Usage Report will provide information on the amount of APIs used for a merge process. This appears as a new column in the generated Composer Usage Report. For more information, see Composer Activity Report

Fixed Issues  

There are no fixed issues in this release.

Known Issues

The following table provides the cumulative list of known issues up to this release. 

Conga Internal IDDescription
PLAPPS-873A merge error occurs when using Lightning Component to merge JSON data in the Composer template.
CM-4662The Right-to-Left (RTL) functionality in the Word template does not work for Composer or Conga Quote Generation (CQG).

When you select templates from the Lightning Component UI, the order in which you select them is not maintained, and they merge at random.

Workaround: Use the TemplateId parameter to specify a template order in the merged document.


All Salesforce Clouds, except Salesforce Community Cloud, support Box integration with Composer in background mode.


All Salesforce Clouds, except Salesforce Community Cloud, support Adobe Sign integration with Composer in background mode.


Send for E-Signature in Adobe Sign integration with Composer using the ESAgreementTemplateID parameter redirects to the home page and fails to send the email. 


When your daily Trigger limit is exceeded, the email alert you are supposed to receive is failing to send.