Turbo Engines for Salesforce June25.04.06 Release Notes
In these release notes, you can find packages, requirements, enhancements, and fixed and known issues for the Turbo Engines June25.04.06 release. For documentation updates, see What's New in Turbo Engines Documentation.
This documentation may describe optional enhancements 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 enhancements and licensing.
Packages
The following packages and dependencies are required to upgrade to this release and use its enhancements. These are the minimum required versions; later versions are also supported. Prerequisites for each enhancement can be found in its documentation. Packages marked (New) are new for this release.
You can register your org for the Conga Upgrade Program, an automated tool that keeps all Conga managed packages in your Salesforce org (production or sandbox) updated to the latest versions. For more information, see Registering for Conga Upgrade Program.
| Package | Latest Certified Version | |
|---|---|---|
| Name | Number | |
Conga Configuration & Pricing (CPQ) | 17.1.2168.35 | 17.2168.35 |
Conga Base Library | 6.1.275.6 | 6.275.6 |
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.
Enhancements
There are no enhancements in this release.
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 |
|---|---|---|
| 00961700 | CPQ-105708 | Publishing activities in Salesforce experience significant slowness when processing large volumes of data, with exceptions such as System.OutOfMemoryException occurring during the process. The issue arises due to querying a large dataset in a single call from the Elastic service, which uses a hardcoded query size value. Additionally, the default scroll size for the Elastic scroll API is set to a high value, contributing to the issue. |
Known Issues
There are no known issues in this release.
DOC ID: CTEJUN25PRN20260407