Status model - work assignment system statuses
This status model can help you understand which basic status transitions are possible on a work assignment. The different system statuses belong to the specific operational stages that a work assignment can go through. By the way, there are more status transitions available than shown, but these have been omitted here to keep the model simple.
 | The outline colors in the diagram represent the colors used on the Resource planner for the various stages of a work assignment. For more information see Resource Planner color legend. |
Preparation stage: initial statuses Planned, Assigned and Accepted. At this point, the engineer has not started the work.
Execution stage: 'in progress' statuses Travel, Work and Paused.
Back-office stage: end statuses Declined, Stopped, Done, Temporary fix. The work assignment is no longer on the app, but returned to the back-office.
Exceptional event: for example status Wait, which might represent an SLA related issue like Stop the clock (SLA ). This status means that the labor hours will not be charged to the customer from this point, until an 'in progress' status is selected again.
| | • Orders supports user-defined statuses. To correctly synchronize orders with work assignments, user-defined order statuses must be mapped to the above system statuses of the work assignment. For more information, see Status mapping and Synchronization between order and work assignment(s). • By configuring an action <-> reason combination, you can enforce field engineers to enter a reason on making a specific status transition. For more information, see Action and reason configuration. |