Antylogic
DemoApp login

399 operational guides

Docs sections
DocsCatalogues
Device

List specifications

Review the specifications available to Harbor Demo Group or Harbor Soho from the Catalogues screen. The Specifications tab lists readable system, organisation and location specifications, supports local search by name, and shows each row with its description, owner and colour or image marker.

In this article

Specifications are product metadata labels such as dietary or catalogue attributes. In Antylogic they can come from the system, the organisation, or the selected location, so the list helps catalogue managers see which records are available before editing products or menus.

This guide covers the list workflow only: opening the Specifications tab, scanning the table, searching by localised name, refreshing or changing page, and opening a row. Creating, editing, deleting or linking specifications to products are separate actions.

Before you start

  • Harbor Demo Group must be selected. For the location route, Harbor Soho or another location must also be selected.
  • The active context must have `catalog:view` for the backend list request. The UI may attempt to load with `catalog:manage`, but the verified list endpoint requires `catalog:view`.
  • Open the screen with `tab=specifications`; if the tab value is missing or invalid, the Catalogues screen opens on the default `catalogs` tab.
  • For a filtered example, use a known readable specification name such as `Vegan` when it exists in the demo runtime.

Instructions

  1. 1.

    Open the Specifications tab

    Go to `/location/catalogs?tab=specifications` for Harbor Soho, or `/organization/catalogs?tab=specifications` for organisation-level catalogue data. The active tab label is `Specifications`.

  2. 2.

    Review the table

    Use the table titled `Specifications` to scan available records. The visible columns are `Name`, `Description` and `Owner`; the name cell includes the colour marker and optional image, while owner shows the location, the organisation or `System`.

  3. 3.

    Search by localised name

    Type in the search field or open `/location/catalogs?tab=specifications&specifications_query=Vegan` to filter the visible rows by localised name. The search is applied in the UI and is not sent to the backend list endpoint.

  4. 4.

    Refresh or change page

    Use the refresh control to request the readable specifications again. When the filtered list is longer than the current page size, use pagination to move through the client-calculated pages.

  5. 5.

    Open a row

    Select a row or use its row actions to open the specification. Read-only rows show `View`; editable rows can show `Edit`, and users with manage permission may also see create or delete actions that belong to sibling workflows.

Validations and limits

  • Without a selected organisation, the screen shows a not-found state; without a selected location, the location route also cannot render.
  • The list includes readable system records, organisation records and, on the location route, records owned by the selected location.
  • System records can be listed and opened, but they are not editable from this scope logic.
  • Search values are trimmed, compared in lowercase and matched against the localised name fallback chain.
  • Changing the search resets `specifications_page` to `1`; invalid or non-positive page values resolve to page `1` and are capped to the available pages.
  • Missing or invalid colour values use the default colour `#0EA5E9`.
  • The Specifications list does not create, update, delete, copy or change product-specification relationships.
  • Specifications do not expose `Copy`; only catalogues and products are copyable in this catalogue surface.

Expected result

The operator can confirm which specifications are readable in the active organisation or location context, filter them by localised name, identify their owner, and open the correct view or edit path without changing catalogue data.

Related articles