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

Crestone Needle

8.263

Conga Batch 

8.25

8.25
Conga Trigger 

8.25

8.25

Important

  • The Composer package has been pushed to all production environments as of October 9th, 2023. This package is fully compatible with the Salesforce Winter '24 release and no action is required for customers.
  • We have identified the Salesforce Winter '24 update will impact composer customers that are depending on the $Api.Session_ID variable to generate documents through Salesforce Flow. It is our recommendation that customers update their Composer Flow solutions from sessionID buttons to Oauth buttons to not be impacted.
  • Moving forward from October, all updates to Composer's Salesforce package are installed automatically in all accounts at the time of release. 
  • Starting October 18th, Composer users in the NA region will be compatible with the Salesforce API Version 58.0. For more details, refer to Support of Salesforce API Version with Composer.
  • Windows OS updates have been applied to AP regions as of 10/18. EU regions have been updated as of 10/25.

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

The following feature is new in this release.

New Parameter: showBoxLogin

For Composer solutions integrated with Box, you can now add the showBoxLogin parameter to determine if the pop-up authorization window for Box will appear for your users. By default, the pop-up window will not appear. For more information, see Box Integration Parameters.

Enhancements

The following enhancements are new to this release.  

Salesforce API Version 58 Support

Conga Composer, Trigger, and Batch now support Salesforce API Version 58. For more information, see Support of Salesforce API Version with Composer.

For this enhancement, you must upgrade the Conga Composer package to Version 8.263, the Conga Trigger package to Version 8.25, and the Conga Batch package to Version 8.25.

Cipher Update for Composer and Salesforce

Conga has updated the cipher suite for Windows Operating Systems for APAC and EMEA regions. 

Fixed Issues  

The following issues are fixed in this release.

Conga Internal IDDescription
COREAPPS-7100Images fail to merge in Composer if the Preview function in Salesforce is unavailable. 
COREAPPS-5525Composer and Batch integrated with Box prompt the User to sign in when launched even if a token has already been generated. 

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 pulled from Salesforce with the &fieldatasource parameter 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).
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-6999

The FieldDataSource parameter is 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: CMPOCT23PRN20231208REVC