When fulfilling orders, Dynamic Revenue Orchestrator (DRO) might need to communicate with external systems. A callout handles that communication.
In the fulfillment step, enter the name of the fallout queue that the step is assigned to if it fails, and the name of the integration definition to launch when the callout runs.
A callout can work synchronously or asynchronously:
- Synchronous: The callout expects an almost immediate response.
- Asynchronous: The callout expects HTTP code
202after you place a request. The callout moves to the In Progress state while it waits for a response.
Use the provider adaptors to generate request payloads from step sources. You can also customize the adaptors. See Callouts in Dynamic Revenue Orchestrator.
To prevent a fatal failure in a callout step when an associated external system is under maintenance deactivate the associated integration definition to put the step is on hold.
- Turn on the Future Dated Steps setting.
- Use the Off-hold Callout Limit setting to define the maximum number of callout steps that can transition from an on-hold state to a ready or scheduled state per minute. This setting controls the batch size when held steps are released after the external system becomes available.
DRO puts the callout step on hold if the associated integration definition is inactive. Callout steps on hold appear on the fulfillment plan so that fulfillment operators and reps can track and act on them. When the integration definition becomes active, the callout steps are released in batches based on the Off-hold Callout Limit setting.