Multi-threaded solving for FSR, tag & name management for runs, and more (v0.31.0)

This new version of the Timefold Platform comes with updates to these Timefold Models:

Employee Shift Scheduling (v1 | Stable)

New metadata in the model run
: Every run will now also have the properties
activeDateTime
and
shutdownDateTime
that keep track of when the solve-phase of a run started and stopped.

Field Service Routing (v1 | Stable)

Enabled multi-threaded solving
: We have enabled multi-threaded solving for this model. Based on our benchmarking results, the maximum number of threads is limited to 4 for now. The desired maximum number of threads can be specified by the
maxThreadCount
attribute in Run configuration. The default is 1.
Visit can specify preferred vehicles
: We have added a capability to specify preferred vehicles for a visit. When set, the visit can be assigned to a shift of one of the specified vehicles if possible. You can specify these as
modelInput.visits[].preferredVehicles
when submitting a new route-plan. Refer to the OpenAPI Spec for details.
New metadata in the model run
: Every run will now also have the properties
activeDateTime
and
shutdownDateTime
that keep track of when the solve-phase of a run started and stopped.

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

Tag & run name management via UI
: You can now edit the name and the tags of a run via the Platform UI (after it’s finished solving). Use this to make specific runs easier to find, or to distinguish between production runs and tests or simulations.
New API endpoint

POST …/{id}/new-run
: Each model now has a new endpoint that allows you to re-run a specific dataset. The endpoint will solve the dataset again, but with the new configuration parameters you submit. This endpoint wants to make it easier to tweak configuration parameters to get to the desired result.
New API endpoint

GET …/{id}/config
: Each model now has a new endpoint that returns all the configuration parameters that were used for a specific run. You can use this endpoint to audit whether different configuration parameters had an effect on the results of different runs.

IP tracked in Audit Log: The Timefold Platform keeps an audit log for administrative actions. (The audit log is not - yet - exposed in the UI.) For safety reasons, we are now also storing the IP of the user that did the action.

docs.timefold.ai

Our documentation website has been updated with the following improvements:

Improved search
: When you use the search on our documentation website, we’ll now only show results from the product you’re looking at. Previously we also suggested articles from other products, which made finding what you were looking for harder.
Dark/Light mode switch
: Go to the footer of the documentation site to choose between light or dark for the documentation website. By default we’re still using the system setting, but if you prefer to override it for this specific site, now you can.

Please let us know if you have feedback.