Version 0073

Updated by Leigh Hutchens

Analytics

Reports

We have added a checkbox for selecting all units in an easy way when creating a report that can include multiple units.

Schedule & Time

Schedule

Advanced settings

Advanced settings are inherited from your shift's shift type, but you may override these on shift level in the "Edit shift" dialog under the "Advanced settings" section.

The following advanced settings can be configured on shift level as of this release:

  • Productive hours
    • This drop-down has three options:
      • "Yes, always" - the shift's hours will count towards "Productive hours", irrespective of the current selection of the "Count as scheduled hours" setting.
      • "Yes, for scheduled time" - the shift's hours will count towards "Productive hours" only if the current selection of the "Count as scheduled hours" setting is true/checked.
      • No - the shift's hours won't count towards "Productive hours", irrespective of the current selection of the "Count as scheduled hours" setting.
  • Count as scheduled hours
    • Determines whether the shift's hours count towards "Scheduled hours". Note the dependency of this setting and that of "Productive hours".
  • Count as worked hours
    • Determines whether the punch linked to this shift counts towards "Worked hours".
  • Free day
    • Checking that a shift is a free day indicates that the assignee of this shift is not supposed to work between the start and end time of the shift. Typically, this setting is checked in combination with unchecking the "Count as scheduled hours" and "Count as worked hours".
If you make changes on shift level and then select a new shift type for your shift, the advanced settings of that newly selected shift type will replace those you set on shift level.

REST API

We have added the possibility to choose if data should be appended or overwritten, appendData true/false if a POST call is done with the same timestamp as previous sent data. This works both for POST /forecast-data and /raw-data.

REST API swagger specification can be found here.


How Did We Do?