CPQ for Salesforce June '26 Release Notes
In these release notes, you can find packages, requirements, enhancements, and fixed and known issues for the CPQ June '26 release. For documentation updates, see What's New in CPQ 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.
For training resources and feature overviews, visit the Conga Learning Center on Conga Community.
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 Approvals (Changed) | 17.0.403 | 17.403.6 |
Conga Base Library (Changed) | 7.1.299 | 7.299 |
Conga Billing (Changed) | 12.1.454 | 12.454 |
Conga CLM Configuration Integration (Changed) | 18.1.203 | 18.203 |
Conga Configuration & Pricing (Changed) | 18.1.2211 | 18.2211 |
Conga Contract Lifecycle Management (Changed) | 17.1.827 | 17.827 |
Conga CPQ API (Changed) | 18.1.139 | 18.139 |
Conga CPQ Approvals (Required if you are using Approvals on CPQ objects) | 13.2.25 | 13.25.4 |
Conga CPQ Maximizer | 10.1.0036 | 10.36 |
Conga CPQ Setup (Required if you are using CPQ Admin Console) (Changed) | 18.1.179 | 18.179 |
Conga Deal Maximizer Setup (Changed) | 8.1.57 | 8.57 |
Conga Deal Maximizer (Changed) | 7.1.10 | 7.10 |
Conga DocuSign API (Changed) | 9.1.147 | 9.147 |
Conga Order Management (Changed) | 1.0.1 | 1.1 |
Conga Promotions (Changed) | 1.0.1 | 1.1 |
Conga Quote Approvals | 7.1.11 | 7.11.1 |
Conga Quote Asset Integration | 6.5.0015 | 6.15 |
Conga Quote CLM Integration (Changed) | 15.1.95 | 15.95 |
Conga Quote Configuration Integration(Required if you are using CPQ and Proposal Management) (Changed) | 18.1.425 | 18.425 |
Conga Quote DocuSign Integration (Changed) | 5.1.24 | 5.24 |
Conga Quote Echosign Integration (You must install the latest Adobe Sign package to use this package) (Changed) | 5.1.21 | 5.21 |
Conga Quote Management (Required if you are using Proposal Management) (Changed) | 16.1.282 | 16.282 |
Conga CPQ (RLS)(Required if you are using Conga RLS Flow to create quotes) | 4.1.130 | 4.13 |
Conga CPQ SPOM Integration | 2.0.19 | 2.19 |
Conga Sales Agent (New) | 0.19 | 0.19 |
Conga Deal Manager (New) | 1.1.7 | 1.7 |
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
The following enhancements are new to CPQ in this release.
CPQ Security Enhancements
As part of Salesforce’s mandatory Security Review requirements for all AppExchange packages, the CPQ packages now enforce stricter security controls. These changes ensure that managed packages comply with current Salesforce security standards and protect customer data from unauthorized access and vulnerabilities. The updates are not optional and are required for continued compliance, support, and future releases.
The security review focuses on user-level data access enforcement, prevention of injection vulnerabilities, removal of deprecated or unsupported libraries, and elimination of session identifiers being passed outside the Salesforce environment to third?party systems. Key security-focus changes are:
- Upgrade to jQuery 3.7
- Removal of deprecated YUI library
- Hardened query handling to prevent SOQL/SOSL injection
- User-context queries for standard objects and fields
- User-mode enforcement for DML operations
- Mitigation of CSRF-related risks
For more information, see CPQ Security Enhancements and Updates in JavaScript Library for Conga CPQ Classic.
Support for Creating Multiple Contracts from a Single Quote
You can now generate multiple contracts from a single quote by filtering quote line items through the Quote to Contract API. This helps you when a consolidated quote includes products for multiple customers that require separate contractual agreements.
To achieve this, you must pass filter parameters (such as a customer or account identifier) along with the quote ID to the Quote to Contract API in the Apttus_QPComply package (QPComplyWebService class). The API creates a contract containing only the line items that match your filter. You can call the API multiple times with different filters on the same quote to create multiple linked contracts.
For more information, see Creating Multiple Contracts from a Quote.
Product Attribute Value Extension (PAVE) Lookup Field
Product Attribute Value Extension (PAVE) object is now available in the Admin UI for selection in lookup field settings, allowing administrators to search and set lookup fields across all PAVE objects. Lookup fields defined on PAVE objects are included as separate records in the turbo request payload, consistent with standard product attribute lookup fields.
For more information, see Lookup Field Settings and Configuring Lookup Field Settings.
Revalidation API Support for Custom Cart Integrations
You can use the getRevalidationLineItems and applyRevalidation APIs to identify and revalidate cart line items based on your chosen criteria. You pass inputs such as Cart ID, Cart Line Item IDs, and custom criteria, and the APIs return detailed responses with product information, revalidation reasons, and errors, if any. This allows you integrate revalidation seamlessly with your custom Salesforce cart implementations.
For more information, see Apply Revalidation and Get Revalidation Line Items.
Server-Side Option Search on Configuration Page
A new execution mode, Option Search Execution Mode, in Config System Properties enables server-side option search on the configuration page. The feature supports searching across both selected and unselected sub-bundles, improving visibility of available options. Matching sub-bundles are highlighted with the count of results, and cross-tab navigation remains supported. Next and Previous actions allow easy navigation through results, with nested sub-bundles clearly indicated for matched options.
For more information, see Config System Properties.
OAuth Authentication for Conga CPQ and Smart Search
CPQ now uses the the JWT (JSON Web Token) flow for authentication OAuth token flow instead of Session Id for authentication with the Conga Merge Service and Conga Smart Search. This change enhances application security and ensures more secure authentication management. Any Session ID passed by custom code is ignored, and the current user name is used to retrieve the OAuth token.
To achieve this, you must have selected the permitted users for Conga SF Connected app and granted Conga SF Connected app to all users.
For more information, see Selecting Permitted Users for Conga SF Connected App and Granting Conga SF Connected App Access to Users.
Introducing Conga Sales Agent
Conga is introducing Conga Sales Agent, a new AI-powered experience built on Salesforce Agentforce. You can now manage quotes, carts, assets, and approvals through natural, conversational interactions without leaving Salesforce. Conga Sales Agent understands your Salesforce context, applies the right defaults, and guides you through complex selling workflows so you can spend less time navigating screens and more time closing deals.
To achieve this, you must configure field visibility, priority, and metadata using Salesforce Field Sets, Permission Sets, and Validation Rules before you can use these features.
- Manage your quotes: You can manage the entire quote lifecycle through Conga Sales Agent using either conversational prompts or familiar UI controls. Conga Sales Agent helps you to perform operations such as create a quote, search for and retrieve quotes, clone a quote, and update a quote.
- Work with your cart from any record page: You can manage carts associated with a quote directly from your Account, Opportunity, or Quote record pages, provided a quote record is linked and the price list is populated. Conga Sales Agent helps you to perform add products or favorites, view your cart summary and line items, and update line items operations in cart management.
- Manage assets end-to-end: You can manage your assets through Conga Sales Agent with the same conversational experience you use for quoting. Conga Sales Agent helps you to perform the search for assets, get asset details, renew assets, and change quantities operations in asset management.
Additionally, you can check whether it requires approval and review the approval details directly in the agent, before you finalize a cart.
For more information, see Conga Sales Agent Overview and Conga Sales Agent.
Fixed Issues
There are no fixed issues in this release.
Known Issues
The following unresolved issues are known to Conga at the time of this release.
| Conga Internal ID | Description |
|---|---|
| CPQ-108205 | When a custom before insert trigger updates line item fields during the clone operation from the bundle configuration page, the updated values are not retained. After the trigger execution, the system restores the line item values from the old map, overriding both OOB and custom trigger updates. |
| CPQ-108019 | Functionality to terminate the asset and get full refund for the whole Asset TCV, instead of refund for the current year, is not working as expected. |
| CPQ-107885 | When performing an Asset-Based Ordering (ABO) operation, the cart may display incorrect serial numbers (line sequence) after products are removed and assets are added again. This issue can result in non-sequential line numbering in the cart. |
| CPQ-107843 | The system does not convert the minimum price defined in the parent Price List to the currency of the derived Price List during pricing calculation in a Based-On Price List configuration. As a result, the system applies the minimum price in the parent Price List currency instead of the derived Price List currency. |
DOC ID: CPQJUN26RN20260529
