NoeVault Snip Category Inheritance

NoeVault Snip Category Inheritance

NoeVault Snip Category Inheritance

NoeVault Snip Category Inheritance Guide

Authority: PR-8.7D.3 / PR-8.7D.4 category inheritance (frozen behaviour)
Composer source: Effective category projection via bootstrap / experience APIs

Concept

Support categories are administered in the platform and inherited / refined for solutions. Snap hosts do not maintain a private category catalogue.

Platform / organisation category administration
        │
        ▼
Effective categories for solution
        │
        ▼
Bootstrap experience.categories  →  Snap composer select

Operator expectations

Task Where
Define / maintain categories Panel category administration (Snap/support category UX)
Verify solution sees correct set Authenticated bootstrap / composer in the host app
Assign ticket category on create Composer categoryId (e.g. General Support = 10 in KP pilot)

Integrator expectations

  • Render categories exactly as supplied by bootstrap experience.
  • Do not hard-code production category IDs in application logic except for tests against a known pilot.
  • If the list is empty or wrong, treat it as entitlement/inheritance/configuration — not an SDK UI bug.

Validation signals

Signal Meaning
Composer shows expected labels Inheritance + publish healthy
Ticket categoryId matches selection Create path intact
Empty list for entitled solution Investigate capability/category publish before changing SDK