Edit an optimisation configuration
Update an existing booking optimiser configuration for Harbor Soho by changing its name, description, default setting and optimiser parameters while Antylogic keeps past services protected automatically.
In this article
Use this guide when an operations manager needs to adjust how the booking optimiser behaves for Harbor Demo Group or Harbor Soho without rebuilding the service setup.
The live configuration keeps the same ID for future services. If past services already used the previous settings, Antylogic can preserve those older values through a historical snapshot in the background.
Before you start
- You are signed in to Antylogic with Harbor Demo Group selected.
- For a location-level edit, Harbor Soho is selected as the active location.
- Your role has optimisation management permission for the organisation or location. View-only access can open the configuration but cannot save changes.
- An active, non-system optimisation configuration exists in the same scope you are editing.
Instructions
- 1.
Open the optimiser settings list
In Harbor Soho, open Reservations and go to the Optimiser settings tab. The list shows optimisation configurations with their scope, default marker, last updated date and row actions.
- 2.
Choose an editable configuration
Open Edit from a non-system Harbor Soho configuration row. Organisation configurations inherited into a location are read-only here, so edit those from the organisation optimisation configuration screen instead.
- 3.
Review the general details
Check the configuration name, description and Default setting. Use a clear name, such as Harbor Soho lunch optimiser, when the configuration supports the Soho lunch service.
- 4.
Adjust optimiser settings
Update only the settings that need to change, such as general behaviour, buffers, objective, splits, risk, saturation, optional choices or alternatives. The form preserves unknown settings keys when it rebuilds the payload.
- 5.
Save the update
Save becomes available when the form differs from the loaded snapshot. When you save, Antylogic sends the trimmed name, trimmed description, Default value and settings to the update endpoint for the current organisation or location.
- 6.
Confirm the refreshed list
After a successful save, the app returns to the configuration list, refreshes the list and detail data, and shows the updated live configuration. Future services that reference this configuration use the new values.
- 7.
Understand historical protection
No extra operator action is required for services that already used the configuration in the past. If needed, Antylogic creates a soft-deleted historical snapshot and rewrites past references while future services stay on the live configuration.
Validations and limits
- Save is disabled for users with view-only optimisation access.
- System configurations and inherited organisation configurations cannot be edited from the Harbor Soho location screen.
- Name is required after spaces are trimmed; the form validates this before the backend call is needed.
- The configuration scope cannot be changed from the edit form.
- The configuration ID used for the update comes from the page URL, not from the request body.
- Save does not ask for a separate confirmation, so review the name, default state and optimiser parameters before saving.
- Normal lists do not show historical snapshot rows because deleted configurations are filtered out.
- Do not present this as a full PATCH flow: the backend requires a non-empty name, and only empty settings have explicit merge behaviour.
Expected result
The live optimisation configuration is updated for its original scope, the list and detail cache are refreshed, future services use the new settings, and past-service settings remain protected when the backend detects affected historical references.