Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

CPQ for Advantage Platform 202609.2.0 Release Notes

In these release notes, you can find enhancements and fixed and known issues for the CPQ 202609.2.0 release. For documentation updates, see What's New in CPQ Documentation.

Note:

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.

Enhancements

The following enhancements are new to CPQ in this release.

Quote Owner Assignment to the Logged-In User

When you create a quote from a Salesforce Account or Opportunity, CPQ now assigns the logged-in user, as the Quote Owner. It also updates the Created By and Modified By fields with logged-in user name. Quote ownership now matches the person who actually created the quote.

For more information, see Quote Ownership Overview and Creating and Configuring Quotes in Salesforce Opportunity.

Summary Deal Guidance Calculation Consistency for Net Price and Margin

Summary Deal Guidance now uses consistent calculations for Net Price From, Net Price To, Margin From, and Margin To values in the guidance popup, aligning them with the summary line’s pricing context across supported measures. For % Margin, the calculations use Net Price and Extended Cost. For % Discount and Discount Amount, the calculations use Extended List Price instead of Extended Price. Custom measures continue to display values as defined in the rules.

For more information, see Creating Guidance Rules.

Option Product Filtering on the Catalog Page

The catalog page no longer invokes GetExcludedOptionIds from ProductFilterCallback, allowing you to add option products directly to the cart. Option filtering now applies only on the configuration page, aligning bundle configuration behavior with the intended flow.

Cart Re-migration Handling in Migrate API

The Migrate API now automatically removes existing in-memory cart data when a migration request is received for a cart already present in memory, then proceeds with migration using the latest cart data. This helps when you need to re-migrate a cart because of data mismatches, sync issues, or a migration that didn't finish, including when you resync an existing Salesforce cart to the Conga Platform. You don't need to delete anything by hand or make any extra API calls.

For more information, see Cart APIs in Conga Developer Portal.

Revalidation of Inactive or Removed Product Line Items and Options in Saved Carts

When a saved cart contains an inactive or deleted Option, the cart is reopened. The Revalidate button is enabled only when EnableRevalidation = TRUE.

The line item status is determined as follows:

If EnableRevalidation = True, DefaultAssetPricing = True, and EnableAutoCancelInactivePLI = TRUE, the affected line item is marked as Cancelled after applying Revalidation, and no refund is issued.

Improved Deep Cloning

Deep Clone now runs on the Conga Advantage Platform, which is the source of truth for cloned quote data. You no longer need the CPQ configuration (QPConfig) package for Salesforce-side cloning logic.

When you deep clone a quote, Salesforce clones only the quote header record, and the complete deep clone occurs on the Conga Advantage Platform. Salesforce receives the cloned data only when required, through reverse synchronization. Earlier, deep clone duplicated quote information in both Salesforce and the Conga Advantage Platform because reverse synchronization had limitations. Reverse synchronization now works reliably, so deep cloning in Salesforce is no longer necessary.

The quote related records, such as quote line items and summary groups, are no longer created directly in Salesforce when you clone a quote. If your custom code, workflows, or business processes depend on these records being available immediately after cloning, they might stop working. Use reverse synchronization from the Conga Advantage Platform to Salesforce to bring the cloned data into Salesforce after platform processing is complete, and validate your customizations

For more information, see Deep Clone Overview.

CCPQ Integration Package Installation Without CLM Dependency

The CCPQ integration package can now be installed independently, without requiring the CLM package or the CLM admin property. This update removes previous installation dependencies, allowing for standalone deployment of the CCPQ package.

To achieve this, Conga introduces a streamlined configuration model for integrating Conga CPQ on the Conga Advantage Platform with Salesforce. Integration settings, endpoint URLs, and JSON-based configurations are now stored in a dedicated custom metadata type named CPQ Integration Settings, which is packaged natively within the CPQ integration package. This enhancement removes the prerequisite dependency on external package admin property objects while preserving your existing integration parameters, settings structures, and quoting workflows.

The legacy Admin Properties configuration method remains supported during this transition period through the automatic fallback mechanism. However, it is deprecated and will be retired in a future release. You are encouraged to migrate your configuration to CPQ Integration Settings custom metadata to ensure uninterrupted compatibility with upcoming releases.

For more information, see CPQ Integration Settings.

Cart Grid Filtering for Primary Charge Lines

When applying filter conditions with "Consider Only Primary Lines" enabled, the cart grid now correctly suppresses secondary charge lines that match the filter, ensuring consistent product filtering and display between Conga Platform and Salesforce Classic.

For more information on enabling Consider Only Primary Lines, see Applying Advanced Filters on the Cart.

Consistent Embedded CPQ Experience Across Salesforce and Microsoft Dynamics

The embedded CPQ experience provides consistent navigation and related list behaviors across both Salesforce and Microsoft Dynamics. All quote-related lists are accessible from Opportunity, Account, and Quote punch-out contexts, with navigation links and contract flows remaining within the embedded frame. Admin and master data links display as non-clickable plain text in both platforms, ensuring a unified and predictable workflow for sales representatives and account managers.

Contract Navigation Within Embedded CPQ

When you use embedded CPQ in Salesforce or Microsoft Dynamics, contract navigation now stays in the same embedded frame instead of opening a new browser tab. Clicking a contract name in the Contracts list opens the Contract Header page in the frame. After you create a contract, the link in the success message also opens in the frame. When you navigate back, you stay in your CRM. In standalone (non-embedded) mode, navigation works as it did before.

Line Item Navigation Within Embedded CPQ

When you use embedded CPQ in Salesforce or Microsoft Dynamics, line item navigation now stays in the same embedded frame instead of opening a new browser tab. Clicking a line item in the Line Items list opens the Line Item Details page in the frame. From there, you can open the Collateral tab and Field Change History without leaving the embedded view. Links in the Field Change History grid now appear as plain text that you can't click. When you navigate back, you return to the Opportunity in your CRM. In standalone (non-embedded) mode, navigation works as it did before.

Revise Cart Action Behavior in Read-Only Mode

You can use the Revise action directly from the main cart grid when viewing a cart in read-only mode, correctly creating and opening a new editable cart version. The Revise action is only visible when the cart is launched in read-only mode, aligning the user interface with expected behavior for finalized and versioned carts.

For more information, see View Cart in Read-only Mode.

Automatic Clearing of Resolved Line Item Error Messages

When you fix a validation error on a line item in Conga CPQ and reprice the cart, the system now automatically clears the error message for that specific line item while maintaining active warnings for any remaining line items with unresolved issues. Additionally, the detailed line-item error responses including the line item ID, message, and error type are available only when the feature flag CPQ-110764-enable-lineitem-error-details is enabled.

Faster Conga CPQ Punchout from Salesforce

The CPQ punchout process from Salesforce now reduces authentication and session initialization time, enabling the Conga UI to load faster. using token caching and parallel processing during session initialization, the updated punchout flow minimizes SSO authentication latency. Cached tokens are securely scoped to your authenticated session and automatically invalidated upon session end or logout. If a token expires or is revoked, you are seamlessly re-authenticated in the background without any visible errors or interruptions to your selling flow.

Rebate Rule Entries API: Restrict Product Scopes for Quantity-Only Benefits

The Rebate Rule Entries API now restricts the All and Family product benefit scopes when the Benefit Type is set to Quantity Only. You must specify individual products or use Ad-hoc Group as the benefit scope. The API provides validation and informational messages when unsupported scopes are selected to prevent performance issues and unintended financial impact.

For more information, see Create rebate rule entries API.

Favorites API: Page, Limit, and Includes Parameters

The Favorites API supports three new query parameters: page, limit, and includes.

  • Use the page parameter to retrieve a specific page of line items.
  • Use the limit parameter to specify the number of line items returned per page. The default value is 50 and the maximum value is 500.
  • Use the includes parameter to specify the line item fields to include in the response.

Examples

GET /revenue-admin/v1/favorites/{favoriteId}?includes=line-items

Returns all available line item details.

GET /revenue-admin/v1/favorites/{favoriteId}?includes=line-items&page=2&limit=200

Returns 200 line items from page 2, corresponding to line items 201 through 400.

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
01046153 CPQ-111914

Auto-included products added via constraint rules are removed from the cart when the Reactivate Cart API is executed on a finalized cart. This occurs because the constraint rule conditions are not satisfied during the reactivation process, leading to the removal of these products.

- CPQ-111913

Option groups with a minimum quantity set to 1 display an error message even when no option is selected, contrary to expected behavior where no error should appear if the minimum option is set to 0.

Known Issues

The following unresolved issues are known to Conga at the time of this release.

Conga Internal ID Description
CPQ-112852

For products with a Default Selling Term configured in PriceListItem, pricing correctly uses the selling term, but the proposal end date is not updated accordingly and instead retains the end date specified on the proposal.

CPQ-112780

When an administrator adds a line item to a cart created by a non-admin user, the pricing callback uses the original user's context to query a custom object. The callback throws a ForbiddenException error when the original user lacks read permission, even if the administrator has the required permissions.

CPQ-112741

When using Cart Grid Version 2 for demos, you may encounter significant UI discrepancies that affect the overall cart experience.

CPQ-112255

Mismatched data in Quote Detail Header TCV vs Detail TCV.

CPQ-108340

When you open a completed collaboration assignment, the More Details link may appear misaligned instead of displaying in the expected centered position.

CPQ-97591

The product name header on the configuration page may stretch too far to the right at 80%, 90%, or 100% zoom, hiding the Summary section. This UI glitch appears while scrolling.

CPQ-95448

The system displays AssetLineItemAttributes on the Installed Products page only after you click the expander icon for each asset, instead of showing them by default.

CPQ-92545

The Auto-Inclusion constraint rule adds the product back to the cart even after it is deleted and a mass update is performed. This occurs regardless of the user’s preference to exclude the product.

DOC ID: CPQRLP202609.2.0RN20261021