System information

APPENDIX Dispatcher
APPENDIX Dispatcher 11
2.3.3.1 Status of orders
The status of orders changes automatically according to the changes in status of services.
The following list shows the various statuses in which a service may be and how this affects
the final order. The priority is from HIGH to LOW.
PRIORITY
STATUS OF THE ORDERS
ordered by the most restrictive statuses
requiring manual operation
HIGH
.
.
.
LOW
ERROR
PAUSED
EXECUTING
PENDING
DONE
For example, in a pending order with 3 services; if 2 are in EXECUTING and 1 in ERROR, the
status of the order is ERROR because this shows that an operator's attention is required.
Services in EXECUTING continue to be executed until they are completed.
Paused devices are also given a high priority on the list above as they require manual
intervention by the operator.
2.3.3.2 Limitations
If "PAUSED" is activated for an order/service, its execution is paused, but other new orders or
services continue to be executed as normal.
If RESUME is activated for an order/service which is PAUSED, in ERROR or DONE, it is
reactivated, and its status becomes PENDING. The order/ service will not be processed until
the Service Module is free again.
It is possible to “KEEP” an order from a Kiosk or Order Terminal to keep it in the system until
it is permanently deleted manually. This is useful for saving sample orders, some interesting
orders from clients you wish to save for some time, etc.
A service with an ERROR status may continue being executed using the RESUME option.
This enables the service to be resumed at the exact point where it left off.
The table below shows all the possibilities for action for orders and services depending on
their status.