Multi-threading support and various other improvements (v0.20.0)

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

Multi-threading support via API
When you start a new run of a model with the API, you can now define the number of threads that can be used by the solver. By using multithreading, you can get better results faster. You can specify the number of threads via the
config.run.maxThreadCount
variable in the JSON payload when starting a new run. Go to your Model’s API Spec page in the platform to learn more.

It’s not yet possible to configure this via the platform’s UI.

We’ve also made the following improvements to the platform’s UI:

Option to specify headers for webhooks
: It’s now possible to configure one or more headers to send along with your webhooks. You could use this feature to send
Authorization
headers.
Configure data retention
: On a tenant’s new Configuration page you can now configure how long run data, audit data, and score events should be stored in your tenant’s database.
Added a Changelog page
: We are introducing a Changelog Page (You’re reading it now) on the platform. We will use this page to communicate new features and changes to the Timefold Platform as well as the models it’s running. Find it via the link in the footer of the platform.
Descriptions for Model KPI’s
: On the “Run Overview” page we have added descriptions to the KPIs of the run to make it easier to understand what each KPI means.
Login with email and password
: In addition to logging in with your Microsoft or Google account, we’ve now made it possible to register with other email addresses.
Various improvements behind the scenes include better error handling and improvements in pod startup time.

This version of app.timefold.ai, includes improvements to the two Timefold Models:

Field Service Routing (v1 - stable)

You now have more fine grained control over the time between dependent visits. It’s now possible to define the minimum delay as a point in time. See Visit dependency with minimum delay as point in time for more details.
Bugfix for the OpenAPI specification validation.

Employee Scheduling (v1 - preview)

This model now has support for defining when contract period rules are valid. Period rules can be used to define the maximum hours per day or per week that employees can work. We have added support to configure when certain period rules are applicable. See Employee contract period rule for more information.
Bugfix for the OpenAPI specification validation.

Please let us know if you have feedback.