In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Conga Composer Platform 2023.12.06 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.
There are no packages required for Conga Composer on Conga Platform.
The following feature is new in this release.
All Composer API Users will need to migrate to the new Conga Platform by January 31st. For more information, see Migrating Composer API to Conga Platform.
The following enhancements are new to this release.
Error codes have been added Conga Composer API error lists, and new error messages have been added. For more information, see Composer API Error Handling.
New Composer Platform endpoints are used after transitioning to Composer API Platform. For more information, see Getting Started with Composer APIs.
There are no fixed issues in this release.
The following table provides the cumulative list of known issues up to this release.
| Conga Internal ID | Description |
|---|
| PLAPPS-873 | A merge error occurs when using Lightning Component to merge JSON data pulled from Salesforce with the &fieldatasource parameter in the Composer template. |
| CM-4662 | The Right-to-Left (RTL) functionality in the Word template does not work for Composer or Conga Quote Generation (CQG). |
| CM-4559 | 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. |
| CM-4622 | 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. |
| 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-9057 | The FieldDataSource parameter is not functioning for customers in NA regions. Workaround: Switching your organization region to EU will allow FieldDataSource to function properly until the issue is resolved. |
DOC ID: CMPOCT23PRN20231211
