Ability to submit a tally for historic shifts where applicable
complete
Jurriaan Persyn
This is a request to be able to submit a tally of historic shifts instead of passing all historic shift data to the model. This would reduce payload size and memory usage while still allowing constraints (such as period rules) to consider past shifts.
The goal is to improve efficiency and simplify input data handling where full historic data is not required.
Log In
Jurriaan Persyn
marked this post as
complete
We’re excited to let you know that this feature is now available since our last release.
Thank you for sharing your feedback, it helps us make Timefold even better for you.
To start using the feature, see https://feedback.timefold.ai/changelog/linked-shifts-and-bulk-time-window-recommendations-in-fsr-historic-shift-exclusi for more details. If you have any questions or further suggestions, feel free to reach out!
Jurriaan Persyn
VP Product
Jurriaan Persyn
marked this post as
in progress
Jurriaan Persyn
Merged in a post:
Ability to have a response without Pinned shifts
A
Alexander Miltenburg (Randstad)
We send a week of unpinned shifts but for WorkingHours Act we need to send 52 weeks in the past and future of pinned shifts. So most shifts that are returned are pinned. We have to filter them. This makes the answer from Timefold much bigger than we need. It would be great if we can tell to Timefold to only send the unpinned shifts back.
Jurriaan Persyn
marked this post as
under review