Configuration and Setup for CME - DRO

Dynamic Revenue Orchestrator (DRO) provides a centralized framework to design and streamline complex order fulfillment. By decomposing orders into manageable tasks, it enables real-time tracking and automated orchestration.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Edition.

Prerequisites

  • During order fulfillment, DRO uses the permission associated ‌with the context definition. For more information, see Create Custom Context Definitions for Order Orchestration.
    Note
    Note To use CME - DRO interoperability, ensure that the org uses the V2 Attribute Model and has migrated to permission set licenses. While Industries CPQ supports Date and DateTime multipicklist data types, these data types are not supported in DRO.
  • Enable CME - DRO Interoperability
    This configuration activates the Dynamic Revenue Orchestrator (DRO) and Inflight features for managing complex order fulfillment and mid-stream changes. It grants necessary user permissions for designing and applying workflows while enabling CME DRO Interop.
  • Configure New ODIN Class for Order Routing
    After the CME org permissions and licenses are active, configure a new ODIN class in the DRO system to route the incoming requests.
  • Set Up Order Routing Rules
    Admins can define routing logic to direct orders to either DRO or OM+. This implementation provides a phased migration. Rules are based on criteria such as product catalog, price list, or product family.