Completed shifts are subsequently consolidated by an asynchronous database job. In this process, different variables are calculated:
This makes it possible to do the following:
Source files from consolidated shifts can be automatically deleted by another asynchronous database job after a configurable time. The configuration is implemented by the Shift Book Admin operator under Shopfloor > Administration > Configuration using the configuration parameters Automatic raw data deletion (activation of deletion) and Deletion offset (time until deletion).
A shift finalization can also be revoked by a role with appropriate permissions. Unlocking shift finalization.
The following diagram illustrates the individual shift statuses and status transitions:
Status transition |
Description |
---|---|
[Non-frozen -> Frozen] |
If auto-finalization is active (Activate auto-finalization configuration parameter), a shift in the past is also automatically finalized (after a wait time as defined in the Auto-finalization offset configuration parameter). |
[Frozen -> Aggregated] |
Consolidating a shift Once a shift is finalized, consolidation is triggered asynchronously in a database job (i.e. calculation of the aforementioned parameters). |
[Frozen -> Unfrozen] [Aggregated -> Unfrozen] |
The shift can now be edited again. A role with special permissions may be required. |
[Unfrozen -> Refrozen] |
(Re-)finalize shift (see Finalizing a shift) A re-editable shift is also automatically re-finalized according to the Re-finalization offset configuration parameter. |
[Refrozen -> Aggregated] |
Consolidating a shift (again) If the source data is still available: Once a shift has been finalized again, consolidation will be triggered again asynchronously in a database job. |
The tooltip for a shift in the calendar view only shows whether or not the shift is finalized. The status of (asynchronous) consolidation in the database is not visible.