Loading
Ongoing maintenance for Salesforce HelpRead More
The Trailblazer Community is now read-only Read More
Get Started with Communications, Media, and Energy & Utilities (CME)...
Run Time Behavior in CME Managed Package and RC Coexistence

Run Time Behavior in CME Managed Package and RC Coexistence

Run time covers what CME MP and RC users actually see and do in the system. The boundary rule differs by operating model. Under separate users, the assigned app (CME MP or RC) is the single source of truth for what each user experiences. Permissions enforce the boundary by restricting each user to their app's surfaces. Under shared users, where a shared user carries both apps (CME MP and RC). Permissions can no longer enforce the boundary, it shifts to the record's differentiator such as record type or SourceApp__c, supported by app-scoped surfaces and validation rules. The differentiator and validation rules are the intended enforcement mechanism under a shared user; because how completely they prevent cross-app record creation depends on your configuration, validate enforcement in your environment. All run-time surfaces such as listing pages, record pages, actions, and automation, should be configured to respect this boundary.

Required Editions

Available in: Classic and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Edition
  • Opportunity, Quote, and Order Capture
    The record type is the differentiator for Opportunity, Quote, and Order. CME MP uses its out-of-the-box record types, while customer implementations must create net-new custom record types for RC. This is necessary because RC has no out-of-the-box record types for these objects, yet the new record picker forces a selection.
  • OM and DRO Order Fulfillment Flow
    Each engine (CME MP or RC) fulfills end-to-end within its own pipeline, but cross-engine account contamination can cause failures, making separate accounts and strict submit-path discipline essential.
 
Loading
Salesforce Help | Article