Creating automated and manual fallout records
With Fallout Management, a provider can create manual or automated fallout records for specific order tasks so that your orders can continue processing through to completion.
Creating automated fallout records
- 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.
- 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 pre-defined 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.
- Create an exception from the order task.
- Enable the revision of the existing order.
- Create an order task.
You can define a workflow that automatically creates fallout records whenever inventory availability issues prevent the fulfillment of order line items.
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.
Create a manual fallout record
Create a fallout record manually for an order task that has a condition or issue that prevents it from being completed.
Before you begin
Role required: sn_fallout_mgmt.fallout_manager
About this task
You can create manual records as needed basis so that you can raise awareness of an issue or condition that is preventing order fulfillment. By creating a record manually, you can also assign it to a person for resolution.
Procedure
Result
- Its State field changes to On Hold, with a comment on which logged-in user caused it to change.
- In the Activity section, a work order note indicates that the order task state has changed from its former state, usually In Progress, to On Hold. A work order note with the message A fallout record FOnnnn has been created also appears.