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.