February '24 Release Notes

Conga Composer for Platform February '24 Release Notes

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

Composer compatibility testing for Salesforce Spring '24 is successful and will not require a new package.

Packages

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

New Features

The following new features are in this release.

Fixing View Counter Link Tracker

An issue can occur for new Platform users with a Composer Salesforce integration where the Document Views field is not updating. For instructions on resolving this issue, refer to Fixing View Counter LinkTracker Feature.

New Parameter - SkipFonts

SkipFonts is a new parameter that allows you to ignore custom fonts in a PDF document. If you are not using custom fonts, SkipFonts reduces merge times for Composer. For more details, refer to Composer Parameter Guide.

New Parameter - SingleDownload

SingleDownload prevents a Composer download URL to be activated a second time. For more details, refer to Composer Parameter Guide.

Enhancements

The following enhancements are new to this release.

Composer API Data Limits

Composer API data limits for maximum JSON payload are up to 10mb. For further details regarding API data limits, refer to Composer API Data Limits.

Composer API Error Handling

Composer API error messages were updated to include new error messages. For further details, refer to Composer API Error Handling.

Fixed Issues

There are no issues fixed in this release.

Known Issues

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.
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.” Workaround: Launch the Global Merge solution manually.
COREAPPS-9832	Document Automation Wizard encounters an error "This page has an error. You might just need to refresh it. Assertion Failed!: Cannot call EnqueueAction() with a non Action parameter. : false Failing descriptor: {APXTConga4:SolutionStep}"

DOC ID: CMPFEB24RN20240207