In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Conga Composer Platform 2023.11.4 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

There are no packages required for Conga Composer on Conga Platform.

New Features

There are no new features in this release.

Enhancements

The following enhancement is new to this release.  

Composer API JSON Payload supports up to 10MB

Composer API JSON now supports payloads up to 10MB in size. 

Fixed Issues  

The following issues are fixed in this release.

Conga Internal IDDescription
COREAPPS-6699Composer SF1 solutions fail on Conga Platform.
COREAPPS-7174SendGrid emails require Conga org provisioning to send merge requests. 
COREAPPS-8157Composer Integration Partner parameters (Google Drive, Box, S3) fail to merge. 
COREAPPS-8181Formula Builder fails to create Formula Field. 
COREAPPS-6990Lightning Component solutions fail with &fielddatasource parameter. 
COREAPPS-8162Batch UI launch button is redirected to Composer Merge UI.
COREAPPS-7100Images fail to merge in Composer if the Preview function in Salesforce is unavailable.
COREAPPS-5525Composer and Batch integrations with Batch prompt Users to sign in even if a token has been previously generated.
COREAPPS-6278Copies of Composer Solutions work in different orgs despite having different endpoints. 

Known Issues

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

Conga Internal IDDescription
CM-4662The 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


DOC ID: CMPOCT23PRN20231102