new

improved

fixed

Timefold Platform

Employee Shift Scheduling

Field Service Routing

Further improvements to rolling time windows contract requirements for ESS and several other improvements (v0.40.1)

Today, we’re announcing version v0.40.1 of the Timefold Platform and models.
This new version of the Timefold Platform comes with these platform improvements:
  • Sticky table header for runs overview
    : When scrolling down your list of runs in the Platform UI, table headers will now stay visible, so it’s easier to know the meaning of the metrics and run properties if you’re comparing lots of runs.
  • We have added a new guide explaining the importance of validating and building trust in an optimized plan. The guide explains which features Timefold offers that help with this.
Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:
Employee Shift Scheduling (v1 | Stable)
  • Further improvements to rolling time windows
    : We have further improved the rolling time windows feature in contract requirements so that you can now also specify hourly time windows for more rules. See “New and noteworthy” for details. This feature can help formulate constraints like: “Maximum 5 days worked in any 168-hour period”, “Maximum 2 night shifts worked in any 168-hour period” or “Minimum 2 consecutive days off in any 168-hour period”.
  • Removed unchanged constraints from the recommendations API response
    : The recommendations API response no longer includes constraintDiffs entries for unchanged justifications to improve clarity and lower the size of the response.
  • We have written a new feature guide about Shift assignments (it goes in detail on the complex task of managing the type and amount of shifts that get assigned).
Field Service Routing (v1 | Stable)
  • Improved break handling
    : Break end times are now exclusive instead of inclusive. This change removes confusion that could occur when a break end time overlapped with a shift start time.
  • Required Breaks API improvement
    : The way of defining required breaks has been deprecated and has been replaced with a simpler alternative that avoids confusion. See “New and noteworthy” for details and instructions on how to upgrade.
  • Removed unchanged constraints from the recommendations API response
    : The recommendations API response no longer includes constraintDiffs entries for unchanged justifications to improve clarity and lower the size of the response.
  • Several bugfixes (including a fix for the visualization).
Please let us know if you have feedback.