New and noteworthy

0.24.0

Model renamed to "Employee Shift Scheduling"

We are renaming the “Employee Scheduling” model to “Employee Shift Scheduling” to distinguish between future other models involving scheduling for employees. (We are not changing API urls or entity names, because …)

Model marked as “Stable”

We have also marked this model as “Stable”, meaning that we promise backwards-compatibility for future minor releases.

"Unassigned shift" constraint no longer includes the shift’s duration in the penalty

We have removed the shift’s duration from the constraint’s penalty. We now only consider the shift’s assignmentPriority.

0.22.0

Added balance by time worked rule

We added a new Balance time worked rule.

Use this rule to make sure the time worked is balanced fairly across employees.

Added employee works shifts with preferred or required tags rules

Tags can now be used to define preferred and required shifts for employees.

See documentation of the rules for more information:

Improved tags documentation

We have improved our documentation related to tags to more clearly give an overview of their possible uses. See Tags and tag types for more information.

Improved performance of balance shift count rule

We fixed an issue in Balance shift count rule, that caused performance degradation for big datasets.

0.21.0

Fixed sequence handling in minutes between shifts rules

We fixed a bug for the Minutes between shifts rules, where the minimum was not always honored for shift sequences.

0.20.0

Period rule can optionally define a validity date time span

Period rule defined as a part of employee contract can now specify a validity date time span to further limit when the rule is applicable.

Please see Employee contract period rule for additional details.

0.19.0

Local date time replaced by date time with offset to UTC

All ISO 8601 local date time types have been replaced by ISO 8601 local date time with offset to UTC (Coordinated Universal Time) to support multiple time zones.

Location constraints

Employees and shifts can now provide a location. This allows you to restrict the possible shifts where an employee can work and minimize the travel distance.

The following constraints have been added:

0.18.0

Shifts worked per period constraints now support employee filtering

Affects the following constraints:

The filtering allows you to include, or exclude shifts worked by specific employee types. For example, you can consider only shifts worked by full time employees.