Download PDF
Download page Conga Composer for Salesforce June24.08.17 Release Notes.
Conga Composer for Salesforce June24.08.17 Release Notes
In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Conga Composer June24.08.17 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.
Packages
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.
Package | Latest Certified Version Name | Latest Certified Version Number |
---|---|---|
Conga Composer | ||
Conga Batch | 8.29 | |
Conga Trigger | 8.29 |
For more information on installing Composer managed packages, refer to Installing Composer Package.
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.
Enhancements
The following enhancement is in this release.
Salesforce API Version 60 Support
Conga Composer, Trigger, and Batch now support Salesforce API Version 60. Composer, Batch and Trigger packages are now available to test the API version 60 in Sandbox environments. Composer users will receive an auto-push of the Composer package on September 14th of Salesforce API version 60. For more information, see Support of Salesforce API Version with Composer.
Fixed Issues
The 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 ID | Description |
---|---|
COREAPPS-3072 | The Right-to-Left (RTL) functionality in the Word template does not work for Composer or Conga Quote Generation (CQG). |
COREAPPS-2027 | 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. |
CM-3679 | All Salesforce clouds, except Salesforce Community Cloud, support Box integration with Composer in background mode. |
CM-3680 | All Salesforce clouds, except Salesforce Community Cloud, support Adobe Sign integration with Composer in background mode. |
COREAPPS-3128 | Conga Quote Generator (CQG) Setup Tab fails to authorize. |
COREAPPS-2223 | Remote Site Settings are not automatically updated correctly. |
COREAPPS-5755 | When your daily Trigger limit is exceeded, the email alert you are supposed to receive is not sent. |
COREAPPS-5451 | The Customize Parameters button in the Composer Solution creator fails when using the Search function and then redirects back to the Conga Composer Solution. While you cannot use the Search function for Parameters, you can still add the parameter from this UI. |
COREAPPS-6998 | Activity Logging parameters are not working in Lightning Component. |
COREAPPS-2349 | With Enhanced Data enabled, using the pre-build solution creation with the Launch Quick Start function will invoke an error: "There was an error processing your request. Something went wrong during the creation of the Composer Buttons. Navigate to the Conga Solution records and create buttons individually for more information." |
COREAPPS-2288 | The DS8 Parameter does not hide the Local Template Tab |
COREAPPS-9633 | Using Global Merge integration with Conga Batch causes an error: "The formula field does not exist. Go to the formula field, select the Set Field-Level Security button, and grant access to the profile of the running user.” |
DOC ID: CMPJUN24PRN20240803