Submit Orders for Decomposition and Order Fulfillment
Sales reps submit orders to Dynamic Revenue Orchestrator (DRO) for decomposition and
fulfillment. During run time, fulfillment operators can track the decomposition and
orchestration plans for submitted orders.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions
Create and Submit an Order Sales reps submit simple or bundled product orders in Dynamic Revenue Orchestrator (DRO) for decomposition and to instantiate the orchestration plan.
Monitor Decomposition During Fulfillment After a user submits an order to Dynamic Revenue Orchestrator (DRO), you can see how products decompose and can spot issues right away.
Fulfillment Step States As steps progress through the fulfillment process, you can check the fulfillment plan to see the state that the steps are in.
View Fulfillment Step History Monitor the changes to a fulfillment step, such as status modifications, on its detail page by using the Fulfillment Step History related list.
Retry or Complete Multiple Failed Fulfillment Steps From a list view or queue, retry or complete multiple steps at once. If you complete a step in this way, the step ignores any errors that can otherwise stop the completion of the step.
Handle Conflicts During Asset Date Amendments by Using Submit Order with Validation Flow It's common to request adjustments to license subscription start dates, either moving them earlier if your users are ready to use them or delaying them if they are not. However, if the order that created the asset has incomplete steps in its fulfillment plan, submitting an asset amendment can result in two orders updating the asset simultaneously. Identify and handle incomplete steps in the fulfillment plan by using the Submit Order with Validation flow.
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.