Creating automated fallout records
With Fallout Management, a provider can create automated fallout records for specific order tasks so that your orders can continue processing through to completion.
- To do so, use the Create fallout action when defining processing scenarios and conditions.
- You can define workflows for the parent records that the order tasks originate from. Generally, order tasks originate from the customer or service orders and order line items.
You might encounter the following scenarios when you are attempting to fulfill customer and service orders.
Scenarios of fallout failures with downstream systems
- The order task sends a request to an external or provisioning system.
- The response from the external system comes back as Timeout or Unable to reach.
You can requeue the task to be sent to the downstream system for processing, up to a predefined number of times. If the error persists after the predefined number of times, you should change the status of the order task to Failed, and then create an incident. You can define a workflow that automatically creates a fallout record whenever you send or retrieve order data to or from an external system that is not available.
Scenarios that involve data problems
- Create an exception from the order task.
- Enable the revision of the existing order.
- Create an order task.
Inventory availability issues
You can define a workflow that automatically creates fallout records whenever inventory availability issues prevent the fulfillment of order line items.
External system issues
Even when the right data structure is submitted in an external system, errors can happen due to the business logic that is implemented in the external system.