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

Preview: CPQ for Advantage Platform 202601.2.0 Release Notes

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

Note:

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 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.

PackageVersion Number
Conga CPQ (RLS)4.130

New Features and Enhancements

The following features are new to CPQ in this release.

Enabling Attribute Rule on Mass Update

CPQ now applies Product Attribute Rules to the Mass Update modal to restrict picklist and multi-picklist values based on line item criteria. Administrators can enable this setting to enforce consistent and valid data selection during mass updates.

Catalog Product Tile View

You can now view the catalog in a tile-based layout, with all existing product actions and details shown on each tile, including a placeholder when no image is available. The tile view is responsive, retains your chosen view across sessions, works across categories and favorites, and lets you open product details by selecting the product name while continuing to honor existing visibility and constraint rules.For more information, see Searching for a product or category.

Enhancements in Send for Signature feature

The Send for Signature feature now defaults the primary contact as the signer and sets the signer type to Signer on the Add Signer page. The system displays clear error messages for unsupported file types and removes the file type message for image files, reflecting that only .pdf, *.doc, *.docx, *.txt, and .rtf files are supported.

For more information, see Sending Documents for eSignature.

Rebate UI: Multi-Condition Rebate Program Creation

You can create rebate programs with multiple independent condition groups using AND/OR logic to support complex combinations of product hierarchies and line item fields. You can define scope, criteria, and aggregation per condition and review all conditions in the summary page for Buy X Get Y programs.

For more information, see Defining Criteria for a Rebate.

Admin API: Updating Incentive Program Settings

Administrators can modify RateTableTierType and MetricValueSource fields for Rebates, Price Programs, and Promotions using the Admin API. The system updates incentive configurations and recalculates cart values based on the new settings without requiring program recreation. Changes apply dynamically across all supported incentive types.

For more information, see Incentive Admin APIs in Conga Developer Portal.

Associated Price Programs Listing on Agreement and Quote Pages

You can view and manage associated price programs directly from the left panel on Agreement and Quote detail pages. The panel supports sorting, searching, column customization, pagination, advanced filtering, bulk actions (disassociate, download), and navigation to program details. The panel shows counts for associated Rebate Programs and Price Programs, and the label “Rebates” is updated to Rebate Programs for clarity.

Cart Group Sub-total Calculation API

The Cart Group Sub-total Calculation API provides sub-totals for each group in the cart, calculated from the net price of all cart lines within the group. The API returns real-time sub-totals, applies group-level price adjustments, and supports bulk retrieval and breakdown of net price and adjustment amounts when group contents change.

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

Selecting Formula Fields in Price Dimension Expression Builder

The Expression Builder in the Price Dimension configuration now displays formula fields from related lookup objects when Context Type is set to Custom. Administrators can select standard, custom, and formula fields retrieved via the metadata API directly in the UI to define price dimension expressions.

For more information, see Creating a Price Dimension.

Setting Line Item Fields with ConstraintRuleActionExpression APIs

Administrators can use the ConstraintRuleActionExpression APIs to define rules that automatically set eligible line item fields when a product is included through the rule engine.The APIs support primary lines and options, allow updating fields such as quantity, and restrict unsupported datatypes including lookup, formula, user, identifier, pricing, and category-related fields.

For more information, see Conga Developer Portal.

RenderDraw Integration Connection in Platform Setup

The RenderDraw integration is now available by default on the platform integrations page, allowing administrators to enable and configure access for third-party visualization tools.

Enhancments in Quote to Contract Integration

You can now create one or more contracts from a quote at any stage of the quote lifecycle. When the "Create Contract" action is triggered, contract with agreement line items (if cart is finalized) is created.All matching fields?including custom and new out-of-the-box fields?between quote and contract objects based on API name are copied.Multiple agreements can be generated from the same quote, and contract line creation supports both synchronous and asynchronous flows depending on the QuoteToContractThreshold setting.Contract can be created irrespective of the status of the cart. However if cart is not finalized, then agreement line items are not generated.

For more information, see Creating a Contract.

Setting Line Item Fields After Including Products via Rules

Administrators can automatically set a line item field when a product is auto-included by an inclusion-type constraint rule with product scope in Advanced Rule Setup. CPQ supports setting one eligible line item field per rule, retains the value when the product is re-added, and resets it when the rule no longer applies.

For more information, see Creating a Constraint Rule Action topic in CPQ for Administrators.

Save Line Item Sort Settings in Cart Views

You can save how your cart line items are sorted as part of each cart view. When you create or update a view, you select a sort field and order. Whenever you switch to that view, your cart automatically applies the saved sort.

For more information, see Working with the cart page.

Import Cart Lines from CSV

You can now import cart line items from a CSV file into your cart using the provided template. You upload the file, and the system validates supported fields (Line Number, Product Name, Product Code, Quantity, Start Date, End Date), showing row-level error messages and highlighting invalid data in red. If there are validation errors, the file is not imported. You can add new products for large carts (100+ lines), and the cart refreshes with pricing for the new lines. You cannot update existing lines, use drag-and-drop upload, perform lookups, or import into read-only or collaboration carts that are submitted for merge, completed, cancelled, or deleted.

For more information, see Working with the cart page.

Reorder Primary Lines within Cart Groups

You can reorder primary cart lines within a group using drag and drop in the full-screen group management view. As you drag, you see valid drop targets and updated line sequences in real time. When you save, the new order is applied to the cart, and related secondary lines stay with their primary line.

For more information, see Working with the cart page.

Introducing Field Display Configuration

Administrators can configure which line item fields are displayed to users during the Service CPQ flow by managing field sets for related line items, asset line items, and line items in Global Settings> Field Sets section. This feature supports adding, removing, and reordering fields, and prevents duplicate field selection, enabling tailored visibility of product, weightage, and pricing information for sales representatives.

For more information, see Configuring Field Set Settings.

Service Eligibility Rule Configuration in Admin UI

Administrators can now define Service Eligibility Rules in the Admin UI to control which service products are eligible for selection based on configurable conditions, such as product type or bundle context. The interface supports specifying rule categories, condition criteria, and action scopes, including product, product group, and product family, with supported match flags for primary lines, options, cart options, assets, and location.

Once administrators set the rule category, the system locks it to preserve rule logic integrity.

For more information, see Creating a Constraint Rule and Adding Constraint Rule Details topic.

Associate Eligible Service Products to Products

You can now associate one or more eligible service products with products and bundles in the cart. You can relate services to an entire bundle or only selected bundle options, and these associations are stored so the UI, pricing engines, and downstream systems can use them. You can also link multiple service bundles to one or more equipment bundles in different combinations. When you remove a service product, its association is removed, and when you remove an equipment bundle, associated services are retained as designed.

For more information, see Working with the cart page.

Storing Transactional Pricing Data

CPQ saves price waterfall transaction details as JSON in the AppliedPriceWaterfall schema when the cart is finalized.Administrators can control this behavior using feature flags, with no impact on performance or existing data, and can extract the data later for custom reporting.

Rebate API: Multi-Condition Rebate Program Creation

Administrators can create rebate programs with multiple condition groups using AND/OR logic across product hierarchies and line item fields. The API supports defining scope, criteria, and aggregation methods, and applies multi-condition programs only to the Buy X Get Y application method.

For more information, see Rebate API in Conga Developer Portal.

Admin API - Dynamic Rebate Scope and Benefit Definition Using Adhoc Groups

Administrators can define rebate scope and benefit recipients using Adhoc Groups alongside existing parameters such as Product, Product Family, and Product Group in the Admin APIs. They can combine multiple parameters, including Adhoc Groups, with AND logic to create flexible, runtime-defined rebate programs that adapt to dynamic business scenarios. This change impacts all application methods and supported tier types.

For more information, see Rebates, Rebate Rules, and Rebate Rule Entries APIs in the Conga Developer Portal.

Support for Default Values in Global Settings for Assets

The following fields in Global Settings for Assets has default value set to “Retain Current Asset End date”. The fields are:Under Amend:

  • End Date Preferences For Change Quantity
  • Default Co-term Option for Change:Quantity

Under Renewal:

  • End Date Preferences For Renewals
  • Default Renewal End Date option

For more information, see Assets.

RLP CPQ Runtime API: Reorder Cart Lines Within and Across Groups

You can now reorder cart lines within the same group or move them to other groups using an updated RLP CPQ Runtime API endpoint. You pass a group ID and an array of primary line IDs in the desired sequence, and the API validates that the lines belong to the specified group, updates the cart line numbers accordingly, and maintains all existing references during the resequencing operation. The API supports partial resequencing (for example, moving only a subset of lines), and returns the updated cart lines with their groups and line numbers so that you can display the new order accurately in your UI.

For more informaiton, see cart APIs in Conga Developer Portal.

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
- CPQ-104082

Service Level field is showing all values in cart lines instead of specific value.

- CPQ-104043

Cloning a product with associated attribute groups, option groups, and numeric expressions incorrectly maps the original product's numeric expression to the cloned product. This causes updates or deletions to the expression to affect the original product instead of the cloned one.

Known Issues

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

Conga Internal ID Description
CPQ-105047

When reopening a saved cart, the Cart hides the scroll bar, which limits navigation.

CPQ-104922

When the Attribute Value Matrix scope is set to Product Group, the system does not evaluate the matrix, so attribute values do not default on the Configuration page.

CPQ-104049

Opening a cart with a large number of line items (e.g., 4,000+) results in a blank screen or browser crash in Chrome.

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: CPQRLP202601.2.0RN20260123