Open Optimizer Configuration

In this article

Before you start

• Harbor Demo Group and Harbor Soho are selected in the GB demo runtime.
• A reservation service occurrence is open from LocationReservationOccurrenceDetail with a valid occurrenceId. In the GB runtime, use BOOKING_DETAIL_OCCURRENCE_ID or BOOKING_OPTIMIZATION_OCCURRENCE_ID.
• The occurrence or its parent service event references an optimizer configuration through optimization_config_id or optimizationConfigId, directly or inside service.
• The operator has reservation:view to load the occurrence, reservation:manage to use the Settings action menu, and optimization:view or optimization:manage to open the optimizer configuration.
• Editing after opening also requires optimization:manage, an editable configuration in the current location scope, a non-historical view and unsaved changes.
• The GB demo occurrence starts on 2 June 2026, so captures taken on 7 June 2026 should open the configuration as a historical, read-only review view.

Instructions

1. 1.

   Open the service occurrence

   From the reservations calendar, open the Harbor Soho service occurrence used for bookings, or navigate to /${ORG_ID}/${LOCATION_ID}/reservations/${BOOKING_DETAIL_OCCURRENCE_ID}?returnRoute=LocationReservationsCalendar&returnMode=week. The occurrence detail must load before the action is available.

2. 2.

   Open the Settings menu

   Use the Settings button in the occurrence header. In the current runtime this may appear as Configuraciones. The optimizer configuration entry is shown only when the service occurrence or event has a non-empty optimizer configuration id.

3. 3.

   Choose Optimizer configuration

   Select the optimizer configuration entry from the Settings menu. If there are temporary table-assignment changes in the schedule, resolve the confirmation first by applying the changes, discarding them or cancelling the navigation.

4. 4.

   Review the configuration

   The destination opens the optimization_config detail associated with the service. It shows the configuration name, description, default flag and optimizer settings. For a past occurrence, Antylogic requests the historical version with occurrence_id and opens the form read-only.

5. 5.

   Return to the occurrence

   Use the back or cancel action on the configuration screen to return to the reservation occurrence detail. Navigation keeps the originating occurrence through returnRoute and returnOccurrenceId.

Validations and limits

• The Settings button is disabled while the screen is submitting changes or when reservation:manage is missing.
• The optimizer configuration menu item is controlled by the presence of optimizationConfigId, not by whether the configuration name query has completed.
• If the service has no optimizer configuration id, the entry is not displayed; if the action is invoked another way, the screen shows an informational message.
• The destination requires optimization:view or optimization:manage; without either permission it shows a no-access state.
• Historical access requires a past service occurrence in the same location, a service event, and an exact match with the requested optimizer configuration id.
• Save is disabled when the view is read-only, the user cannot manage optimization, the item is not editable in the current scope, or no form values have changed.
• Opening the screen does not run the optimizer, assign tables, change reservations or save optimizer settings.

Expected result

The operator reaches the optimizer configuration linked to the service occurrence, reviews the rules used by that service, and returns to the same occurrence without changing bookings or optimizer settings unless they explicitly save permitted edits later.