List and Search Optimisation Configurations

In this article

Before you start

• The operator is signed in with an active organisation context; the location route also needs an active location context.
• The operator has `optimization:view` or `optimization:manage` for the relevant organisation or location scope.
• For GB captures, use Harbor Demo Group and Harbor Soho in the localised demo runtime with the supplied `ORG_ID` and `LOCATION_ID`.

Instructions

1. 1.

   Open the optimiser settings list

   Open Harbor Soho reservation settings and choose the `Optimizer` tab. The shared list loads the optimisation configurations available to the current location; the organisation route opens the same list in organisation scope.

2. 2.

   Read the scope of each row

   Use the name, scope, default status, and updated date columns to understand where each configuration applies. System templates are always readable, organisation rows apply across Harbor Demo Group, and location rows apply to Harbor Soho.

3. 3.

   Search the visible configurations

   Use the search field to filter the loaded rows. The filter is local to the screen and matches only the configuration name and displayed scope label. For a stable GB demo capture, use `Sistema` because seeded system templates include names such as `Sistema - OFF`.

4. 4.

   Use pagination when needed

   Move between pages when the filtered list is longer than one page. If filtering leaves the current page out of range, the screen moves to the last valid page.

5. 5.

   Understand permission mode

   With `optimization:view`, the operator can see the table and open rows. With `optimization:manage`, the operator also sees `New configuration` and row actions such as edit, copy, and delete where ownership rules allow them. This guide stops at review and search.

Validations and limits

• The location route requires both organisation and location context before loading; the organisation route requires organisation context only.
• The API returns the complete optimisation configuration array for the selected scope. `query`, `page`, `page_size`, and `pageSize` are screen parameters, not API search or pagination contracts.
• Default status appears only when `is_default` is true. The updated date uses `updated_at` and falls back to `created_at`; empty or invalid dates show as `-`.
• Soft-deleted configurations are excluded from the normal list.
• System rows cannot be edited or deleted, and organisation rows inherited into the location list are visible from Harbor Soho but not editable or deletable from the location scope.

Expected result

The operator can review the optimisation configurations available to the current organisation or location and narrow the visible list without changing operational data.