Use the Mixed Mode setting to selectively enable high-performance Standard APIs for
specific functions. Keep complex, custom workflows in Classic mode. Accelerate adoption with lower
risk. Based on high user usage, we've grouped the three most popular Cart APIs such as
getCartsProducts, getCartsItems, and getCartsItemsById together.
Required Editions
Available in: Classic and Lightning Experience
Available in: Enterprise, Unlimited, and Developer
Edition.
User Permissions Needed
Permission required to access Mixed Mode:
CME Managed Package license
Admins can use a single toggle at the group level to switch these APIs between Standard and
Classic modes. Replace the restrictive global toggle with a granular control, allowing a phased
transition to Standard Cart APIs. This flexible approach preserves backward compatibility and
helps businesses modernize their systems at a pace that suits their specific technical
readiness.
From the App Launcher, find and select Vlocity CMT
Administration.
From the Custom Settings, find and select Enable Features.
Click Configure on the Standard Salesforce libraries
and cache with the CPQ Cart-Based APIs.
Enable the Standard Cart APIs in the Mixed Mode setting.
Use Case Scenario for Mixed Mode
A Telco provider optimizes high-volume cart performance while preserving complex legacy logic
by splitting API execution between the Standard and Classic engines.
Action: Admin switches Cart Item Management to Standard engine for high-speed throughput and
keeps Checkout and Order Submission on Classic engine to support legacy hooks.
Result: High-traffic "Add to Cart" requests use the high-performance Standard engine, while
the system seamlessly switches to the Classic engine during checkout to execute specialized
customizations.
A media company uses a "Selective Rollback" to fix a pricing calculation error during a
high-traffic sale without losing the performance gains of other upgraded APIs.
Action: The Admin switches only the Pricing APIs group back to Classic mode while keeping
other high-volume groups, like Cart Creation, on the Standard engine.
Result: Use the Mixed Mode setting to selectively enable high-performance Standard APIs for
specific functions. Keep complex, custom workflows in Classic mode. Accelerate adoption with
lower risk.
A customer adopts new Salesforce features incrementally by selectively upgrading only the
latest Standard Cart APIs while maintaining established integrations on stable settings.
Action: Admin enables the specific subset of APIs provided in the new release level within
the CPQ settings, leaving older, existing logic in its current configuration.
Result: The business integrates innovations at its own pace and tests release-specific
capabilities without risking the stability of the entire cart infrastructure.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.