Configure runtime architecture and several smaller improvements (v0.43.0)

Today, we’re announcing version v0.43.0 of the Timefold Platform and v1.1.0 of the Timefold models.

This new version of the Timefold Platform comes with these platform improvements:

Ability to configure machine type to run the solving operations
: When you set-up a configuration profile, you can now also apply extra scheduling policy labels that let you choose between running solve operations on AMD64 or ARM64 architecture. Configure specific machine types to find the best runtime for your type of dataset and learn which one yields better results.

We have improved the Maps service documentation with more detailed information on availability of maps.
Several smaller improvements (including logging more relevant data in the Audit log, more clearly indicating configuration parameter precedence when doing a new run, more clearly indicating for which models API keys can be used, and showing score analysis details when all constraints are satisfied, showing icons for constraint groups) and bugfixes (including returning the right better response headers for Recommendation API calls for non-existing runs).

Next to that, this new version of the Timefold Platform comes with updates to these Timefold Models:

Field Service Routing (v1 | Stable)

Icons for constraint groups
: The score analysis and configuration profiles UI have been updated with icons for each of the constraint groups to help make each of the model features more clear.

We have added documentation that explains how to handle long-running visits.
We have made several smaller bugfixes (to the visualization in the platform) and improvements (like not showing the Visit SLA metric if no SLA information is provided).

Employee Shift Scheduling (v1 | Stable)

Icons for constraint groups
: The score analysis and configuration profiles UI have been updated with icons for each of the constraint groups to help make each of the model features more clear.

We have made several smaller bugfixes (to the visualization in the platform and we fixed a bug that caused the solver to not respect the shift rotation constraints in some edge cases).

Please let us know if you have feedback.