Download PDF
Download page Conga Turbo Engines for Salesforce October '24 Release Notes.
Conga Turbo Engines for Salesforce October '24 Release Notes
In these release notes, you can find packages, requirements, new features and enhancements, and fixed and known issues for the Turbo Engines October '24 release. For documentation updates, see What's New in Turbo Engines 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.
To access the learning path, including overviews and demonstrations of this release’s updated features and enhancements, visit the Conga Learning Center.
Packages
The following packages and dependent packages are required to upgrade to this release to utilize all the new features of this release. These are the minimum required versions; later versions are also supported. Separate prerequisites for each feature can be found in the respective guides. The packages marked as (Changed) are new in this release.
| Product | Latest Certified Version Name | Latest Certified Version Number |
|---|---|---|
Conga Base Library (Changed) | 5.2.269 | 5.269 |
Conga Configuration & Pricing (Changed) | 16.2.2144 | 16.2144 |
System Requirements and Supported Platforms
For requirements and recommendations to consider before installing the Conga product suite, see the System Requirements and Supported Platforms Matrix.
New Features and Enhancements
The following features are new to Conga Turbo Engines in this release.
New Admin Setting to Manage Favorites with Large Bundles
A new admin setting, APTS_EnableFavoriteExecutionWithTurbo, along with the getFavoriteConfigurationData remote action to add favorites to the cart. This prevents duplicate entries when adding large bundles and favorite groups together.
For more information, see Configuring Admin Settings.
Enhancement to the Charge Types
The custom field value on the newly added Non-primary charge line is no longer copied from the Primary charge line. Instead, the system ensures that the custom field on the Non-primary charge line remains independent to prevent any data inconsistency between charge lines. This improves the accuracy of the line item details and aligns with expected business logic.
Previously, when you use multiple charge types in the Price List Item, driven by Attribute Values, a Turbo Callback is set up to populate a custom field on the Line Item. However, when the charge type criteria are satisfied, and a new charge type line item is added, the custom field value from the Primary charge line is unintentionally copied to the new line item, which leads to incorrect data.
Support for Price Ramps with 'Usage' Price Method
Pricing Administrators can create Price Ramps using either the 'Recurring' or 'Usage' Price Method.
The system now allows Price Ramps with the 'Usage' Price Method when 'Enable Ramps' is set to TRUE. Previously, only the 'Recurring' Price Method was supported.
Code Line Numbers in Debug Logs
Debug logs now show code line numbers regardless of the UI exception feature flag. This change allows you to identify issues without turning off the is-callback-exception-throw-enabled flag.
Custom Measures on the Deal Guidance Pop-up Window
The pop-up now displays only the “#CustomMeasure From” and “#CustomMeasure To” columns, without referencing 'Net Price From' and 'Net Price To'. For the Custom Measure, the Deal Guidance pop-up shows these two columns exclusively. Previously, the pop-up showed both the From and To measures alongside their respective From and To prices.
Fixed Issues
The following issues are fixed in this release. If any actions are required, they will be listed in this table.
| Case Number | Conga Internal ID | Description |
|---|---|---|
| 00873163 | CPQ-78208 | The Salesforce’s standard field limit validation message does not appear as intended on the cart page. When the field limit on the cart page is crossed, CPQ displays the validation message and disappears immediately. |
Known Issues
The following unresolved issues are known to Conga at the time of this release.
| Conga Internal ID | Description |
|---|---|
| CPQ-87590 | CPQ does not trigger the inclusion rule that is associated with a rollup summary field on the product configuration record as intended. |
| CPQ-87044 | When you re-finalize the cart, CPQ does not create the usage tier record. When you finalize the cart after adding a product for which usage-based PLI and Matrix are configured, CPQ creates the UsageTier records as expected on the lineitem record. But, If you try to reconfigure the finalized cart that leads to cloning the configuration and UsageTier records and finalizing the cart again, CPQ does not create the UsageTiers records on the new finalized configuration’s lineitem records. |
| CPQ-82781 | CPQ does not remove the validation error message on the cart page even though the required conditions are met from the validation callback class. |
| CPQ-82068 | When you invoke the |