These are the various states a job may be in, as it moves through its life cycle in response to events occuring. The job states are closely related to the JobStatusEvent that immediately proceed them.
A job moves through the states in this order : UNASSIGNED > ASSIGNED > DISPATCHED > RECEIVED > ACCEPTED > ENROUTE > STARTED > PRE_SIGNOFF > COMPLETED
A job may only progress forward through these states, never backwards, excepting the following special circumstances:
- At the STARTED stage, it may be placed into ON_HOLD state for a break or other reason, and resumes back to the same STARTED state.
- A job may be recalled from the field worker after it has been ACCEPTED, or the worker is ENROUTE, and optionally may be forced if the field worker has already reached the STARTED state, whereby the job will be removed from the field worker, and return to ASSIGNED state, ready to be dispatched to the same, or another, field worker.
- A job may be REJECTED by a field worker rather than ACCEPTED, in which case the job returns to UNASSIGNED state, ready to be ASSIGNED and DISPATCHED to another field worker.
The data fields of this object.
|ACCEPTED||String||The job has been accepted by the field worker.|
|ASSIGNED||String||The job has been assigned to a particular field device, but has not yet been dispatched.|
|COMPLETED||String||The job has been completed by a field worker.|
|DISPATCHED||String||The job has been dispatched out to a field device/worker.|
|ENROUTE||String||The field worker is enroute to the job.|
|ON_HOLD||String||The job has been placed on hold.|
|PRE_SIGNOFF||String||The job has been progressed to the point where the job has been finished, but has not yet been signed off.|
|RECEIVED||String||The job has been received by the field device of the field worker.|
|STARTED||String||The job has been started by the field worker.|
|UNASSIGNED||String||The job has been created on EService, but has not been assigned to a field worker yet.|