Platform UX improvements, shift pattern improvements for Employee Shift Scheduling, and more (v0.27.1)

This new version of the Timefold Platform comes with the following improvements:

Subscribe to get changelog notifications
: We are now using a new system for changelog communication. Please use the subscribe button to get notified about new releases. Additionally, you can now filter the changelog on components or types of updates.
Improved Model Run Logs
: The Logs page of a Model Run now contains only the output of the Timefold Solver itself.
Confirmation before deletion
: When deleting items in Tenant Settings via the Platform UI (e.g. webhooks, or api keys), we now require users to type the name of the item they’re deleting. We’ve added this extra layer of confirmation for destructive actions that cannot be undone to prevent mistakes.
Hardened Tenant Selection
: Users that are in multiple tenants should no longer experience problems switching between tenants. We have made the tenant id part of the Tenant Settings pages’ urls so that you can have multiple tabs open from different tenants as well as share urls with colleagues.
Various UX Improvements
: We have done several UX improvements to the Platform UI, including improved feedback when actions are being submitted, items are being refreshed, when you reached the maximum amount of concurrent model runs, or when navigating through different steps in modals.

The new version also comes with updates to these Timefold Models:

Employee Shift Scheduling (v1 | Stable)

Improvements to shift patterns
: We have fixed multi-day shift pattern rules to correctly handle a pattern starting with
OFF
. See New and noteworthy for details. The
REQUIRED
multi-day patterns are now deprecated and will be removed in a future version in favor of
PREFERRED
patterns with a high weight.
New demo data set showing multi-day shift patterns
: When you start a new run, you now have the option to start a run of a demo data set that showcases the multi-day shift patterns feature. This dataset demonstrates a problem where 2 employees have a contract with 2 types of multi-day shift patterns: Day Call and Night Call.
“Assigned Shifts”, “Working Time Fairness” and “Disruption Percentage” KPI’s added
: For new runs of the model, you’ll see that 3 new KPIs became available in the output, as well as visualized in the platform. You can use these KPIs to compare the quality of the provided planning solutions. Here is a description of the new KPIs:
“Assigned Shifts”
: The number of shifts assigned to an employee in this schedule.
“Working Time Fairness”
: This percentage indicates how fair a given solution is in terms of how many hours employees are assigned. The higher the percentage, the more equally distributed the working time is between employees. The value is null if no fairness rules were defined.
“Disruption Percentage”
: When an existing schedule is posted, this KPI represents the percentage of shifts that were disrupted, i.e. assigned a new employee. If the provided schedule didn't have any assigned shifts, the value will be 0%.
We have added Employee contracts and Pairing employees feature guides to our documentation, explaining how to use these powerful features.

Field Service Routing (v1 | Stable)

We have added a video explaining the Field Service Routing model to the Introduction documentation.
Small bugfix.

Please let us know if you have feedback.