Order Status

Each order has a status, determining where it is in the processing cycle:

StatusDescription
PendingNewly created ‘shell’ order without line items, work orders and new services yet created, or

  • an order with line items created but without services and work orders, or
  • with line items created but work orders have not been started yet.
In ProgressOrder execution started, at least one work order is in progress.
CompletedAll work related to work order completed.
CanceledOrder 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:

Order building blocks and their relationships
Order building blocks and their relationships

The following rules apply to order status calculations:

  1. A new order is always created with the Pending status
  2. 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)
  3. It is not possible to or delete line items to the order in a final status (Canceled, Completed)
  4. Order status is calculated as follows:
InputOrder Status
Empty order, no line itemsPending
Line items added, but work orders for line items not yet createdPending
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 canceledCanceled
All line items created and all work orders final and at least one of them is completedCompleted
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.

Was this page helpful?