Fulfillment Step Types

Fulfillment steps are defined in the fulfillment workspace. For more information on how to create fulfillment steps, see Define Orchestration Plan Components.

As you create your fulfillment steps, use the following references to understand how the different fulfillment types function.

• Auto Task Fulfillment Step
  Use auto tasks to process data automatically as part of your orchestration plan. An auto task fulfillment step requires a Salesforce Flow to perform the automation.
• Callout Fulfillment Step
  When fulfilling orders, Dynamic Revenue Orchestrator (DRO) might need to communicate with external systems. A callout handles that communication.
• Manual Task Fulfillment Step
  Add a manual task to orchestration when you need user input at a particular place in the fulfillment flow. For example, when you need an approval sign-off or manual enrichment of data. Dynamic Revenue Orchestrator (DRO) can assign a manual task to a user or a queue.
• Milestone Fulfillment Step
  A milestone represents a point in the fulfillment process between different flows of control, and is completed when all of its dependencies have been completed. For example, you can use a milestone to indicate a fulfilled order, at the end of your orchestration plan.
• Pause Fulfillment Step
  The pause step stops fulfillment until certain conditions are in place. Set the Resume On rule to something that must be true before the pause step completes.
• Staged Assetize Step
  To independently assetize standalone or bundled products, even if other order line items are in process use a staged assetize step. The staged assetize step is typically applicable for long-running orders that span many hours, days, or even weeks.