Retain Approval Status During Quote-to-Contract Cart Cloning

The EnableQuoteToContractCopyCart feature flag is introduced to retain the approval status of the source cart when cloning a cart in the Quote-to-Contract flow. When enabled, the cloned cart keeps the approved status, avoids unnecessary approval cycles, and allows agreement and agreement line item creation for finalized carts. To manage feature flag, you must update configuration using the Update a configuration API.

For more information, see Config Management APIs in Conga Developer Portal.

Faster Large Cart Retrieval with Cursor-Based Pagination

You can retrieve large carts faster from the Object Database using cursor-based pagination. Instead of counting all records before fetching data, the system uses a bookmark-style approach to load items in sequential batches reducing database load and improving performance for carts with thousands of line items.

This applies to Get Cart Items, Checkout to Order, and Abandon Cart operations when using the Object Database. You can enable or disable this via a feature flag without disrupting existing behavior

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

Cart Finalization Validation for Cancelled or Inactive Assets

The Finalize button in the mini cart and cart is now disabled if any asset in the cart is in Cancelled or Inactive status. An error message displays during finalization and the Finalize button is re-enabled after removing the affected assets.

Read-only Cart View for IT Roles in CPQ WebUI

Users with the DEBUGGING USER or CONFIGURATOR roles now access the cart in read-only mode if they do not have UPDATE permission on the ProductConfiguration object. The cart displays all product lines, quantities, pricing, and totals, while editing controls are hidden or disabled and a "View only" indicator is shown. Users with edit permissions continue to access the editable cart as before.

For more information, see Manage Roles and Permission Groups.

Pagination Support for Groups

You can retrieve group data in manageable pages using the Metadata API. This pagination support enables you to efficiently handle large group datasets without fetching all records at once.

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

Attribute Based Constraint Rules APIs for Optional Attribute and Option Groups

The APIs for Attribute Based Constraint (ABC) Rules now supports creating rules without specifying an attribute group or option group. When no attribute group is provided, attributes in the rule entries must belong to the bundle product. The APIs also enforce immutability for product, attribute group, and option group fields after rule creation, and updates validation and uniqueness handling for rules with null scope values.

For more information, see Create Attribute Constraint Rules, Update Attribute Constraint Rules, and Create Attribute Constraint Rule Entries APIs.

Upsert and Miscellaneous Line Item Support in Cart Import API

You can update existing cart line items and create new ones in a single CSV import using the POST {{/api/cart/v1/{version}/carts/{cartId}

/import}} endpoint. If a row in your CSV includes a line item ID, the API updates that existing line item; if no ID is provided, the API creates a new line item. You can also import Miscellaneous (non-product) charge line items such as sales tax, fees, or adjustments without specifying a product code. Additionally, the API now returns row-specific error messages when CSV parsing fails, helping you quickly identify and fix the problematic row. The PATCH import endpoint is deprecated; use the enhanced POST endpoint for all import operations going forward.

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

Cart Versioning Support for Order and Agreement Objects

You can use cart versioning for Order and Agreement business objects. Versioning for these objects is controlled by the tenant-level cart versioning configuration, ensuring consistent behavior across Order and Agreement carts, including superseded, abandoned, and cloned carts. The existing Proposal object-level versioning behavior remains unchanged.

Rolled-Up Net Price Support for SUM Aggregation

The SUM aggregation method in Price Program criteria now correctly evaluates rolled-up Net Price values when the scope includes both bundle and option line items. This update prevents duplicate aggregation, ensures accurate program eligibility evaluation, and avoids pricing stage sequencing issues.

For more information, see Defining Scope and Defining Criteria.

Asset Callback Feature Flags Migration to CPQ Feature Settings

As part of the 202607.2.0 release, Asset Callbacks that are currently managed through feature flags are migrated to CPQ Feature Settings. After upgrading to 202607.2.0 release, the feature flags listed below will no longer be used. Instead, the corresponding CPQ Feature Settings will control Asset and Renewal Callback functionality.

If any of the above feature flags are currently enabled, configure the corresponding CPQ Feature Settings after upgrading to 202607.2.0.

All CPQ Feature Settings are disabled (false) by default. Use the following API to enable the required settings:

PATCH /api/revenue-admin/v1/feature-settings

The API supports updating one or more CPQ Feature Settings in a single request by specifying the required values in the payload.

For more information, see Asset Callback Class and Asset Renewal Callback Class.

Automated Validation for Collaboration Requests

You can use the On Collaboration Request Async Callback to automatically manage validation errors when creating or updating Collaboration Requests. This feature allows you to remove or update errors related to zero Net Price line items without triggering a pricing recalculation, ensuring a smoother workflow for your collaboration processes.

Attribute Length Field for String Data Type

Administrators can now define a character limit for attributes of the String data type using the new Length field when creating attributes. An error message is displayed if a default value exceeds the specified character limit.

For more information, see Creating an Attribute.

Configure Sync Modes and Monitor Sync Health for Account and Contact Objects

You can now manage account and contact sync behavior from a single configuration entry point, eliminating the need to navigate individual recipe settings. For each object, you can switch the sync mode Off, Punchout only, Periodic, or Real-time and pause or resume sync without disabling the underlying recipe. A sync health dashboard gives you at-a-glance visibility into the last sync timestamp, records processed, and error count per object. All configuration changes are logged with the user and timestamp for full audit traceability.

Attribute Based Constraint Rules: Include a Product

Administrators can configure attribute-based constraint rules to automatically add or remove products in a bundle when specified attribute combinations are selected or modified. The system evaluates and applies these rules, supporting attribute groups and option groups as context while enforcing minimum and maximum limits for option groups. This feature supports AVMs, PARs, CRs, and other attribute-based constraints, and applies only to options within bundles.

For more information, see Attribute Constraint Rules and Attribute Constraint Rules Entries APIs in Conga Developer Portal.

Real-Time Event-Driven Sync for Account and Contact Records

You can synchronize Account and Contact records from Dynamics 365 to Conga in real time using Dataverse webhooks or plugin triggers. Conga automatically reflects the latest CRM data when records are created or updated. You can configure real-time or scheduled synchronization independently for each object, and only modified fields are processed during synchronization.

Cart Status Validation for Quote Cloning

Administrators can now configure which cart statuses are eligible for the Clone Quote operation when the AllowQuoteCloneForAllCarts system property is set to false. By default, only carts with statuses such as Saved, Finalized, Pending Approval, Ready for Finalize, and Approval Required are eligible, but additional statuses can be included as needed. This update prevents errors by ensuring only carts with acceptable statuses are cloned with quotes.

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

Asset Status Validation on Cart Finalization

The status of each asset during cart finalization is validated. If any asset in the cart is cancelled or inactive, an error message displays the asset ID or name and its status, preventing order activation with invalid assets.

ACV Calculation Displayed On Quote Details and Cart Page

Annual Contract Value (ACV), for subscription-based deals, for Standalone and Bundle Products is displayed on the cart page for every cart line item.

Annual Contract Value (ACV) for products is calculated using the formula ACV = Total Contract Value / Contract Duration (in years) and displayed as a field for each cart line item. The system recalculates ACV after each pricing change, supporting bundles, options, rollup lines, recurring, one-time, and ramp line items.

The total ACV for the quote is displayed in the Basic Information tab.

Example: If Total Contract Value (TCV) = $4500 and total Contract Duration =5 yrs then ACV=4500/5= $900

For more information, see Annual Contract Value and Cart in Grid View.

Agreement-Based Asset Amendments

You can amend or perform Change operation on assets created from Agreement flow.

Endpoint: {{baseUrl}}/api/asset/v1/assets/{{cartId2}}/change

Body : ["AssetID"]

Asset Creation from Agreement

Create assets directly from the Agreement object for all product types, including standalone, bundle-option, and ramp using Agreement cart line items. Asset line items automatically copy Account, ShipTo, and BillTo details, and each asset line item generates a corresponding transaction record. The associated Order includes the Agreement number for reference.

The flow is as follows:

1. Create quote
2. Activate cart
3. Add line items
4. Finalize cart
5. Create Agreement from Quote using the API: baseUrl/api/quote/v1/quotes/cartId/agreement
6. Create Order from Agreement using the API: baseUrl/api/order/v1/agreements/AgreementID/create-order?isasync=false
7. Activate the Order. This will create assets.

Service CPQ: Associate Service with Equipment using API

You can now configure and sell Services for existing Equipment assets using the below listed API. This enhancement enables sales representatives to select existing Equipment assets and associate Services to them, streamlining the service attachment process within a single transaction.

Upon Service asset creation, the system automatically establishes a relationship between Equipment assets and Services using the Related Asset Line Item object, enabling accurate tracking and management of asset-service relationships.

{{baseUrl}}/api/cart/v1/carts/{{cartId2}}/items/{{servicelineid}}/related-items

Deal Guidance Rules Using Price Recommendations

Administrators can configure Deal Guidance rules using out-of-the-box and custom measures that calculate the variance between Net Price and recommended Floor, Ceiling, or Target prices. The system provides real-time visual indicators to salesrep on the cart line item during quoting, helping them make pricing decisions that align with business objectives.

For more information, see SPOM-Based Pricing Guidance in Deal Guidance.

Relate Button on Installed Products Page

The Relate button is available on the Installed Products page, allowing salesrep to select any active asset and access the Service Catalog. The button remains enabled when selecting different assets, supporting seamless navigation to related services.

For more information, see Working with the Service Cart.

Cart View Access Control API (Protected Views)

You can use the Cart View Access Control API to create protected cart views and assign access to specific users or roles. Protected views are non-public by default and cannot be modified or deleted by end users. You can assign, retrieve, update, and remove user and role access through the API. The API validates user and role existence, enforces unique assignments, maintains user-view and role-view relationships, and applies default view precedence and access filtering based on the IsAdmin request header.

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

Image Support for Attribute Picklist Values

Attributes now display images for picklist and multi-select picklist values when an image is associated with the value. The feature supports JPG, PNG, and SVG formats up to 2 MB, maintains a 1:1 aspect ratio, and follows attribute visibility rules during selection.

For more information, see Creating an Attribute.

Display Custom Totals on Cart Grid

The Display Custom Totals on Cart setting in Config System Properties lets you display totals for up to three custom fields in the Cart Grid and Summary totals section instead of the out-of-the-box totals. The application calculates and displays only the configured custom field totals while continuing to display subtotals and totals for summary lines.

For more information, see Retrieve custom settings associated with a flow and Update custom settings associated with a flow.

Delete Favorites via Admin API

You can delete one or multiple inactive favorites using the Delete Favorite Admin API (/api/revenue-admin/v1/favorites). The API supports bulk deletion of up to 1,000 records per request. Only favorites marked as inactive are eligible for deletion. When a favorite is deleted, its associated product configuration and cloned line items are automatically removed without affecting the original source cart or its line items. If any active favorite is included in a bulk delete request, the entire operation fails and no favorites are deleted

For more information, see Revenue Administration APIs in Conga Developer Portal.