Loading
Feature degradation | Gmail Email delivery failureRead More
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Dynamic Revenue Orchestrator for Business Processes

          Dynamic Revenue Orchestrator for Business Processes

          Use Dynamic Revenue Orchestrator (DRO) to design and orchestrate any object regardless of whether is is based on a sales transaction. Review the differences between sales transaction-based and non-sales transaction-based business process orchestration setup.

          Required Editions

          Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
          Available in: Enterprise, Unlimited, and Developer Editions
          Feature Sales Transaction Business Process Non-Sales Transaction Business Process
          Sample use cases Quote to Order, Order to Cash, Incidents, Cases, Service Requests Dunning Process, Obligations Management, Compliance Verification
          Primary goal Streamline the standard sales-to-service lifecycle Streamline the pre and post-sale workflows
          Object origin Derived from the Product2 object Independent of Product2 object. For example, Collection Plan or Obligations.
          Context definition Extends Sales Transaction context definition Defines a custom context definition or extends a standard context definition, such as Billing, with the required mapping.
          Orchestration type Predefined Sales Transaction usage type Predefined Generic Orchestration Type
          Note
          Note Dynamic Revenue Orchestrator supports multiple rule libraries based on the plan usage type. The system identifies the correct library using specific API naming conventions: DRORuleLibrary for the default fulfillment plan usage type, and DRORuleLibrary[UsageTypeName] for others. If your existing default rule library uses an API name other than DRORuleLibrary, create a new library with the API name DRORuleLibrary and migrate your rules to it. Failure to do so prevents you from creating, editing, or executing rules.
           
          Loading
          Salesforce Help | Article