Open a Service Occurrence

In this article

Before you start

• You are signed in with an organisation and location selected, for example Harbor Demo Group > Harbor Soho.
• The selected location has a service entry in the reservations calendar, such as Soho lunch service.
• Your role has location-level `reservation:view`. `reservation:manage` is not required to open the occurrence, but it controls follow-up actions inside the detail.
• For direct demo captures, the runtime provides `BOOKING_DETAIL_OCCURRENCE_ID`, `RESERVATION_OCCURRENCE_ID` and `SERVICE_OCCURRENCE_ID`.

Instructions

1. 1.

   Open the reservations calendar

   Go to the reservations calendar in week mode for the selected location. This is the operating entry point for service occurrences and shows service entries alongside reservation density for the visible date range.

2. 2.

   Select the service entry

   Choose the service card you want to operate. Service entries open reservation occurrence detail; private events open the calendar event editor, and vacation or unsupported entries do not open this flow.

3. 3.

   Let Antylogic resolve the occurrence if needed

   When the selected service has no occurrence id yet, the app resolves it from the event id, occurrence start, start time and end time. The backend may return an existing matching occurrence instead of creating a new one.

4. 4.

   Confirm the occurrence detail

   Check that the detail header matches the intended service date, service name, time window and status before working with reservations, table assignments or service operations.

5. 5.

   Use the operating tabs

   Use List, Timeline and Summary to review the service. The detail loads reservations, table assignments, customers and open service sessions, and conditionally loads tickets, layout, optimisation configuration and the latest optimisation run.

6. 6.

   Return to the previous surface

   Use the back action to return to the calendar or source surface. When opened from the reservations calendar, the return route preserves the calendar mode and visible dates where available.

Validations and limits

• Opening the occurrence requires `reservation:view`; `service:view` may expose the calendar preset but is not enough to load occurrence detail.
• The app only attempts occurrence resolution when `eventId`, `occurrenceStart`, `start` and `end` are present and valid dates.
• The backend requires `event_id`, `starts_at` and `ends_at`; `ends_at` must be later than `starts_at`. If `occurrence_start` is omitted, `starts_at` is used as the occurrence start.
• Missing organisation, location or occurrence id shows a not-found state in the detail page.
• Occurrences from another location, empty occurrence ids and occurrences whose calendar event is not a service are rejected.
• Users without `reservation:manage` can read the detail, but management actions such as creating reservations, changing states, changing settings and assigning tables are disabled.
• Past occurrences can be opened for review, but automatic reservation creation is not enabled for past days.
• If calendar resolution fails, the frontend remains on the calendar and does not show a dedicated visible error for this action.

Expected result

The operator lands on the service occurrence detail with the service header, status and operating tabs loaded, ready to review reservations and table context for the selected Harbor Soho service.