Antylogic
DemoApp login

399 operational guides

Docs sections
DocsReservations
Device

Resolve a Public Service Occurrence

Open a public service such as Harbor Soho's Soho lunch service from the Reservations calendar or Location Home. Antylogic resolves or reuses the service occurrence in the background and opens the reservation occurrence detail for operational review.

In this article

A scheduled public service becomes operational when it is connected to a service occurrence. The occurrence detail is where the reservation team reviews bookings, tables, service state and summary information.

Use this guide when a reservation operator or location manager needs to open the Soho lunch service without manually creating backend records or deciding whether the occurrence already exists.

Before you start

  • The operator is signed in to Harbor Demo Group and working in Harbor Soho.
  • The operator has reservation viewing access for the active location.
  • The selected item is a public service event, not an internal service, private event or holiday block.
  • The service item has a service event id plus valid start and end times. If an occurrence id is already present, Antylogic can open it directly.
  • For GB captures, the runtime has SERVICE_EVENT_ID, SERVICE_OCCURRENCE_ID and SERVICE_OCCURRENCE_START available.

Instructions

  1. 1.

    Open the Reservations calendar

    Open Harbor Soho's Reservations calendar in week mode and locate Soho lunch service. The calendar loads public service entries and occurrence metadata when reservation visibility is available.

  2. 2.

    Select the public service

    Select Soho lunch service. If the item already has an occurrence id, Antylogic opens the occurrence detail. If it does not, Antylogic resolves the occurrence from the service event and time window before navigating.

  3. 3.

    Review the opened occurrence

    Use the reservation occurrence detail as the operational view for the service. This is where the team reviews reservations, table timeline and summary information for the selected service occurrence.

  4. 4.

    Understand reuse versus materialisation

    When a matching occurrence already exists, Antylogic reuses it. When none exists, it materialises an open General occurrence from the public service event without creating reservations or table assignments.

  5. 5.

    Use Location Home when available

    A Location Home service card follows the same rule. Existing occurrences open directly; services without an occurrence id are resolved before opening the reservation occurrence detail.

Validations and limits

  • The resolve call is protected by reservation:view for the active location.
  • Only public service events run this resolve path. Internal services, private events, holiday blocks and non-service calendar entries do not resolve to reservable occurrences.
  • The backend requires event_id, starts_at and ends_at, and ends_at must be after starts_at. If occurrence_start is omitted, starts_at is used as the occurrence anchor.
  • The implemented route is POST /api/app/{orgId}/{locationId}/reservations/occurrences, returning a ServiceOccurrenceView with occurrence and event.
  • This action reads the calendar event and reads or creates the service occurrence only. It does not create reservations, customers, table assignments, tickets or service sessions.
  • The current GB runtime already has SERVICE_OCCURRENCE_ID, so standard captures prove the open or reuse path rather than a fresh materialisation branch.

Expected result

The operator lands on LocationReservationOccurrenceDetail for the selected public service occurrence, with reservation occurrence state refreshed and ready for review.

Related articles