Save Service Capacity References
Save the visibility and capacity references that make a service bookable: public or internal visibility, required Layout and Catalog for public services, and optional Optimisation. Internal services remain planning blocks, so the current UI hides and clears the public capacity controls.
In this article
Use this guide when preparing or editing a Harbor Soho service such as Soho lunch service for reservations and service operations.
The service form saves these references through the service bundle flow and stores them on calendar_event.payload. They determine which floor layout, catalogue and capacity mode apply to the service.
Before you start
- Work inside Harbor Demo Group and the Harbor Soho location.
- Have service management access for the location.
- Open a service event from the Services calendar; other calendar event types do not use these capacity reference fields.
- For a public service, make sure a Layout and Catalog exist. In the GB demo, use Demo floor plan 1 and Soho Menu where available.
- Use Manual mode when no optimisation configuration should be saved. Selecting an optimisation configuration requires reservation automation access.
- The service or selected occurrence must not have started.
Instructions
- 1.
Open the services calendar
Open the Services calendar for Harbor Soho, then create a new service or open an existing service that is still editable.
- 2.
Create or edit the service
Use the service form to review the title, date and time range. New service drafts start as Public and preselect the default or first available Layout and Catalog when available.
- 3.
Set public capacity references
For a public service, keep Visibility set to Public, then choose the Layout and Catalog that should be used for capacity, bookings and service operations.
- 4.
Choose Manual mode or Optimisation
Leave Optimisation blank for Manual mode, which saves no optimization_config_id. Select a non-system optimisation configuration only when automatic reservation optimisation should apply.
- 5.
Save the service
Save the form. Antylogic stores visibility, public layout_id, public catalog_id and optional optimization_config_id on the service event payload through the service bundle save flow.
- 6.
Use Internal for planning blocks
When Visibility is changed to Internal, the UI clears Layout, Catalog and Optimisation, hides those controls, and saves the service as an internal planning block instead of a publicly bookable service.
- 7.
Choose recurrence scope when prompted
For recurring services, choose whether the change applies only to the selected occurrence or to future services. Recurring edits go through the split flow with the same service bundle payload.
Validations and limits
- A title is required and the start time must be before the end time.
- Public services require both Layout and Catalog before they can be saved.
- Layout and Catalog references must be valid UUID values when sent to the backend.
- Manual mode omits optimization_config_id; a non-empty optimisation configuration must be a valid non-system configuration and requires reservation-automatic:use.
- The current UI clears and omits capacity references for internal services, although backend validation can accept valid internal references sent by another client.
- Started services cannot be updated from this flow.
- A public service with active reservations cannot be changed to internal for affected current or future occurrences.
- There is no standalone capacity-reference endpoint; the save happens through service bundle create, service bundle update, or recurring split.
Expected result
The service stores the correct capacity references on calendar_event.payload. Public services can feed booking, availability, TPV and optimisation flows; internal services remain private planning blocks.