Each order has a status, determining where it is in the processing cycle:
Status | Description |
---|---|
Pending | Newly created ‘shell’ order without line items, work orders and new services yet created, or
|
In Progress | Order execution started, at least one work order is in progress. |
Completed | All work related to work order completed. |
Canceled | Order was cancelled entirely (if some work orders have been completed and some canceled, the order status is Completed). |
To understand order status, it is important to understand Nextian order structure, and that activity information is tracked on three levels: order, work order and individual task; it is not tracked on a line item though.
Order structure can be visualized as follows:
The following rules apply to order status calculations:
- A new order is always created with the Pending status
- Creation of services/work orders does not change the order status; it remains in Pending or In Progress (the change is triggered when work orders transition from Pending to other status)
- It is not possible to or delete line items to the order in a final status (Canceled, Completed)
- Order status is calculated as follows:
Input | Order Status |
---|---|
Empty order, no line items | Pending |
Line items added, but work orders for line items not yet created | Pending |
Line items created (i.e., work orders created but in still in Pending status) | Pending |
At least one line item is in progress (i.e., associated work order is In Progress) | In Progress |
All line items created, and all work orders canceled | Canceled |
All line items created and all work orders final and at least one of them is completed | Completed |
Important Service fulfillment status is separate from order (and work order) status and is not taken into consideration while calculating order status. For new service flows, a typical scenario is to either automate service start via an automated task or enforce a completion condition that a task must be started. Another reason for not using service status is that that ‘widget’ products do not create a service. |