Antylogic
DemoApp login

399 operational guides

Docs sections
DocsCatalogue setup
Device

View Specification

Open a catalogue specification to check its name, description, colour and image in the current organisation or location scope.

In this article

Specifications help catalogue teams label product attributes with a name, description, colour and optional image. At Harbor Soho, operators use the Specifications tab to find the right attribute before it is used with products.

This guide covers viewing the detail only. A specification may be editable or read-only depending on ownership, system status and permissions, but the operator can still confirm the visible fields when read access is allowed.

Before you start

  • Harbor Demo Group is selected as the organisation.
  • Harbor Soho is selected when working in the location catalogue.
  • The user has `catalog:view` for the current organisation or location context.
  • A readable specification exists in the current scope, inherited organisation scope or system scope.

Instructions

  1. 1.

    Open the specifications list

    From catalogue setup, open the Specifications tab for the current scope. At location level, Harbor Soho can show location-owned specifications, inherited organisation specifications and system specifications.

  2. 2.

    Choose the specification

    Use the row for the required specification. The list helps identify it by name, description, colour and owner where those columns are visible.

  3. 3.

    Review the detail form

    Open the detail page and check the fields rendered by the app: Nombre, Descripción, Color and Imagen. If an image is attached, it is shown from the linked file.

  4. 4.

    Recognise read-only cases

    System specifications, deleted records, read-only route contexts and specifications outside the user's writable scope appear without a save action. Use the page to verify the information, not to force an edit.

Validations and limits

  • The detail only loads when the organisation or location context is present and the selected specification is readable from that scope.
  • Backend detail access requires `catalog:view`; `catalog:manage` alone is not proven sufficient by the backend evidence.
  • A specification from another organisation or unreadable location is treated as not found.
  • Name and colour are required when the same shared screen is used for editing, but viewing the detail does not send an update payload.

Expected result

The operator confirms the specification's visible name, description, colour and image without changing specifications, files or product associations.

Related articles