View an allergen
Open an existing allergen from the catalogue area to review its name, description, colour and image in the current organisation or location context. This is a read-focused action; creating, saving changes and deleting are handled by separate actions.
In this article
Use this guide when a catalogue manager needs to check the details of an allergen that already exists for Harbor Demo Group or Harbor Soho.
The detail page keeps the operator in the Allergens catalogue context. It can show editable controls for users with management access, but viewing the page does not change the allergen until a separate save action is used.
Before you start
- You are signed in to Antylogic.
- Harbor Demo Group is selected as the organisation.
- Harbor Soho is selected when opening the location catalogue route.
- An allergen exists in a readable scope for the current context: system, organisation or location.
- Your role has catalogue view access for the current scope.
- The detail route includes an allergen id; opening the no-id route starts the create flow instead.
Instructions
- 1.
Open the Allergens tab
From Harbor Soho, open catalogue management and select the Allergens tab. Use the list to find the allergen before opening its detail page.
- 2.
Open an existing allergen
Select the allergen row or its view/edit action. Antylogic opens the detail page for that record and keeps the return context on the Allergens tab.
- 3.
Review the allergen details
Check the saved name, description, colour and image state. If the allergen has an `image_file_id`, the preview is loaded through the file service; otherwise the image field has no preview.
- 4.
Check read-only cases
Use the page only for consultation when the allergen is a system allergen, belongs to a scope you cannot manage, or the page is opened in forced read-only mode. Users without detail access see a no-access state instead of the form.
- 5.
Return to the Allergens tab
Use the page back action to leave the detail. Antylogic returns to catalogue management with `tab=allergens` preserved, so the operator can continue reviewing allergens.
Validations and limits
- `routeParams.id` must be present to treat the screen as the detail of an existing allergen.
- `selectedOrgId` is required; in the location route, `selectedLocationId` is required as well.
- The detail request requires `catalog:view` before the allergen is read.
- The allergen must be readable in the current scope. In a location context, system, organisation and same-location allergens are readable; allergens from another scope are treated as not found.
- System allergens are readable but not editable from this page.
- Name and colour are the key required fields shown by the form; an empty or invalid saved colour falls back to a neutral grey display.
- The image preview depends on `image_file_id`; allergens do not use a separate `image_url` field.
- This action does not create, save, delete or manage product-allergen associations.
Expected result
The operator reviews the existing allergen and returns to the Allergens catalogue tab with no allergen data changed.