CRM · Segment categories

Simple CRUD for the taxonomy used to group segments, so long segment lists stay navigable.

AreaCRM
Routescrm.segment-categories · crm.segment-categories.index · crm.segment-categories.new · crm.segment-categories.edit
Centre modulescrm
Staff levelsroot · admin · manager · crmmanager
Modelssegment-category
UI labeltitle.header.crm.segment-categories / menu.navbar.segment-categories.show
Coverage2 use cases · 1 happy · 2 failure

How it works

A minimal list (name + edit/delete) built on the standard nf-crud + routes/form.js pattern; deletion goes through the shared confirm-deletion service.

Use cases

Why someone opens this (2)

  • Separating lifecycle segments from campaign segments and employee segments.
  • Keeping a centre’s segment list organised as it grows.

Path map

flowchart LR
    F(["Segment categories"]):::feat
    F --> H1["Category created and assigned"]:::ok
    F -.-> X1["Name missing"]:::bad
    F -.-> X2["Deleting a category still in use"]:::bad
    classDef feat fill:#157068,stroke:#157068,color:#ffffff,font-weight:bold
    classDef ok fill:#e3f1ea,stroke:#0d6b42,color:#0d4a2e
    classDef bad fill:#f7e6e2,stroke:#9a2d1c,color:#6e1f13

Happy paths

Category created and assigned

  1. User creates a category with a name.
  2. routes/form.js#saveModel validates and saves, then returns to the list.
  3. The category becomes selectable in the segment builder.

Failure paths

QA checklist

Tick these off while regression-testing this feature. The boxes are plain Markdown, so progress is visible in git diffs.

  • ✅ Category created and assigned
  • ⛔ Name missing
  • ⛔ Deleting a category still in use

Implementation


Generated from doc/feature-inventory.json · id crm-segment-categories · commit 276788ca6