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
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 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.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
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.