Core TSIs : Work assignments : Concepts : Status model - work assignment system statuses
Status model - work assignment system statuses
This status model can help you understand which basic status transitions are possible on a work assignment. There are more status transitions available, but these are left out here to keep the model simple.
Diagram showing the available status transitions for work assignments
Legend
Red & green: end statuses. The work assignment is at the back-office, no longer on the app.
Grey: statuses indicating the preparation phase. The engineer has not started the work.
Blue: statuses indicating that the work is being executed / in progress.
Yellow: statuses indicating exceptional events, like Stop the clock (SLA ).
* 


•    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.
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. See Supporting data > Action - reason configuration for more information.