Antylogic
DemoApp login

399 operational guides

Docs sections
DocsCatalogs
Device

View catalog detail

Open an existing organisation or location catalog to review its name, default status, image, selected products and product type order. The screen becomes editable only when the operator has manage permission for the catalog owner and the catalog is not forced into read-only mode.

In this article

Catalog detail is the place to inspect the menu structure that a location or organisation already uses. It brings together the catalog identity, its products and the order in which product types appear during service.

For the GB demo, use Harbor Soho and the Soho Menu catalog. This guide is for review only: saving, deleting, copying and historical review are separate actions.

Before you start

  • The operator is signed in and an active organisation is selected.
  • For the location route, an active location is selected.
  • The operator can access the catalog area through `catalog:view` or `catalog:manage`; the backend detail request requires `catalog:view`.
  • An accessible catalog id exists. In the GB demo runtime, use `SETUP_CATALOG_SOURCE_ID=2e6563c2-1621-4c65-8da3-213d7f4e6aaf` and `SETUP_CATALOG_SOURCE_NAME=Soho Menu` for Harbor Soho.
  • For a meaningful review, the catalog should include products and product types.

Instructions

  1. 1.

    Open the catalog area

    From the active scope, open Catalogs. Use the Harbor Soho location catalog area for the Soho Menu demo catalog, or the organisation catalog area when the catalog belongs to the organisation.

  2. 2.

    Select an existing catalog

    Choose the catalog row or its View/Edit action. The detail route must receive an effective id; without one, the same screen switches to create mode instead of opening this action.

  3. 3.

    Review the catalog identity

    Confirm the requested catalog name, default setting and image field. The implemented form labels these fields as `Nombre`, `Predeterminado` and `Imagen` even in the English runtime.

  4. 4.

    Review catalog products

    Scroll to Products to see which products belong to the catalog. The table can be filtered by search, product type, tax category, allergen, specification and price; Harbor Soho examples include Fish and chips, Beef pie and Sticky toffee pudding.

  5. 5.

    Review product type order

    Use `Orden de tipos de producto` to understand the sequence used for selected product types, including TPV tab order. The backend returns this order from `catalog_product_types.sort_order`.

  6. 6.

    Recognise read-only and error states

    The same detail screen becomes read-only when the route forces `readOnly=true`, the catalog is deleted, or the operator lacks `catalog:manage` for the catalog owner. Missing context, missing read permission, failed loading or an inaccessible owner scope prevent normal detail review.

Validations and limits

  • The detail action requires an effective catalog id; without it, the component enters create mode.
  • The UI does not request detail if there is no catalog id, no scope context or no frontend access permission.
  • The backend `GET` requires `catalog:view` and hides catalogs from other scopes by returning not found.
  • Location detail can read location-owned catalogs and catalogs from the active organisation, but edit permission is based on the real owner of the catalog.
  • Read-only mode disables the name, default and image fields, hides product selection, disables product type dragging and removes Save and Delete actions.
  • The normal detail request has no payload and does not modify `catalogs`, `catalog_products` or `catalog_product_types`.
  • Copying, updating, deleting and historical review belong to sibling actions, not to this detail review flow.

Expected result

The operator can inspect the Soho Menu catalog identity, products and product type order without changing data. Edit controls appear only when the active user and the catalog owner allow management.

Related articles