Feature Requests

Ability to define custom priorities and weights for shifts. Whenever the model needs to choose between multiple shifts to assign to an employee, it will favor shifts with higher priority.

This is a request to support compression of payloads sent to the Timefold APIs as well as when receiving data from the Timefold API with the goal of making it faster to send big payloads.

This is a request for the platform to send a webhook notification when a model run finishes. This way there is no longer a need to poll the API, but solutions can be received in near-realtime.

Default use of the Employee Shift Scheduling model will try to assign an employee to each shift. This feature request that the scheduling is done based on the extra input of an hourly demand curve. In this type of planning it's not important that all shifts are assigned, but that the assignments make sure a demand curve is followed as closely as possible.

This is a request to make assigning employees to shifts fairer by optimizing for equal distributing of hours between the different employees in a schedule.

This is a request for the platform to support multi-threading when solving a model run.

When deleting an item in Tenant Settings (e.g. webhook, or tenant member), there is a simple configuration dialog. Making a mistake is thus easy, especially since there is often no way to restore the deleted item. This request is to confirm the deletion via an extra step where the user has to type the name of the item that is being deleted.

This is a request for improved demo data sets that showcase specific features of both the Employee Shift Scheduling model, as well as the Field Service Routing model. Before running a demo data set, it should be clear what the demo data set will show.

This is a request to implement paging for the model runs overview, so you can go further back in time when going through previous runs.