---
id: FAS-CRM-ACT-04
feature: FEAT-CRM-ACT-04
product_area: crm
module: activities-tasks
revision: 1
status: proposed
product_intent: proposed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  rhythm-v2-docs: 18a49edf30ee6bda18b159b65a2b91e093ea713d
capabilities:
- CAP-CRM-ACT-016
scenarios:
- id: FAS-CRM-ACT-04-01
  title: Maintain type and queue catalogs as complete lists
  kind: behaviour
  exercises:
  - CAP-CRM-ACT-016
  relies_on:
  - ATS-CRM-ACT-016-02
  - ATS-CRM-ACT-016-03
  - ATS-CRM-ACT-016-05
  preconditions: An administrator owns several unused task types and queues.
  steps:
  - do: Create classifications and queues, then reorder each complete list.
    exercises:
    - CAP-CRM-ACT-016
    provenance: proposed
    source: services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
  - do: Read both lists and try an incomplete reorder.
    exercises:
    - CAP-CRM-ACT-016
    provenance: proposed
    source: services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
  expected: Valid complete orders persist and rejected incomplete lists move no records.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to: []
  provenance: proposed
  source: services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
- id: FAS-CRM-ACT-04-02
  title: Inactive configuration continues supporting service work
  kind: interaction
  exercises:
  - CAP-CRM-ACT-016
  - CAP-CRM-ACT-010
  - CAP-CRM-ACT-012
  relies_on:
  - ATS-CRM-ACT-016-07
  - ATS-CRM-ACT-012-09
  preconditions: An inactive task type and queue already exist.
  steps:
  - do: Create a task naming them, then claim its waiting work.
    exercises:
    - CAP-CRM-ACT-016
    - CAP-CRM-ACT-010
    - CAP-CRM-ACT-012
    provenance: proposed
    source: services-crm:modules/tasks/services/persistence/tasks.ts
  expected: The service accepts both operations; configuration inactivity does not establish a routing
    refusal.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to: []
  provenance: proposed
  source: services-crm:modules/tasks/services/persistence/tasks.ts
- id: FAS-CRM-ACT-04-03
  title: Protect configuration referenced by work
  kind: lifecycle
  exercises:
  - CAP-CRM-ACT-016
  - CAP-CRM-ACT-010
  relies_on:
  - ATS-CRM-ACT-016-04
  preconditions: A task names a customer type and queue.
  steps:
  - do: Attempt to delete each configuration record.
    exercises:
    - CAP-CRM-ACT-016
    - CAP-CRM-ACT-010
    provenance: proposed
    source: services-crm:modules/tasks/services/persistence/task-types.ts; services-crm:modules/tasks/services/persistence/task-queues.ts
  - do: Remove the task, then delete its unused type and queue.
    exercises:
    - CAP-CRM-ACT-016
    - CAP-CRM-ACT-010
    provenance: proposed
    source: services-crm:modules/tasks/services/persistence/task-types.ts; services-crm:modules/tasks/services/persistence/task-queues.ts
  expected: Referenced deletion conflicts; after work removal the unlocked customer configuration can
    be deleted.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to: []
  provenance: proposed
  source: services-crm:modules/tasks/services/persistence/task-types.ts; services-crm:modules/tasks/services/persistence/task-queues.ts
- id: FAS-CRM-ACT-04-04
  title: Refuse maintenance without administrator authority
  kind: permission
  exercises:
  - CAP-CRM-ACT-016
  relies_on:
  - ATS-CRM-ACT-016-01
  preconditions: A caller can only read task types.
  steps:
  - do: Request a task-type reorder through the API.
    exercises:
    - CAP-CRM-ACT-016
    provenance: test
    source: services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
  expected: The route returns Forbidden and leaves the list unchanged.
  negative: true
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-015
  provenance: test
  source: services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
- id: FAS-CRM-ACT-04-05
  title: Keep customization when task seeds are repeated
  kind: regression
  exercises:
  - CAP-CRM-ACT-016
  relies_on:
  - ATS-CRM-ACT-016-08
  preconditions: Customer values already exist under baseline task-type identifiers.
  steps:
  - do: Apply task-type baseline seeds repeatedly.
    exercises:
    - CAP-CRM-ACT-016
    provenance: test
    source: services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js
  - do: Read the existing entries.
    exercises:
    - CAP-CRM-ACT-016
    provenance: test
    source: services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js
  expected: Existing configuration remains unchanged instead of being replaced by seed defaults.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to:
  - TST-CRM-ACT-022
  provenance: test
  source: services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js
- id: FAS-CRM-ACT-04-06
  title: Queue configuration determines available views and creation context
  kind: interaction
  exercises:
  - CAP-CRM-ACT-016
  - CAP-CRM-ACT-014
  - CAP-CRM-ACT-012
  relies_on:
  - ATS-CRM-ACT-014-02
  - ATS-CRM-ACT-012-02
  preconditions: A named active queue exists and a contributor can create work.
  steps:
  - do: Open that queue view and create work without changing its suggested queue.
    exercises:
    - CAP-CRM-ACT-016
    - CAP-CRM-ACT-014
    - CAP-CRM-ACT-012
    provenance: proposed
    source: react-console:components/console/tasks/definition.tsx; services-crm:modules/tasks/services/persistence/task-queues.ts
  - do: Deactivate the queue and reload available views; inspect the task through the API.
    exercises:
    - CAP-CRM-ACT-016
    - CAP-CRM-ACT-014
    - CAP-CRM-ACT-012
    provenance: proposed
    source: react-console:components/console/tasks/definition.tsx; services-crm:modules/tasks/services/persistence/task-queues.ts
  expected: Creation retains queue context; the inactive queue view disappears while existing work retains
    its routing.
  negative: false
  data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar
    changes.
  bound_to: []
  provenance: proposed
  source: react-console:components/console/tasks/definition.tsx; services-crm:modules/tasks/services/persistence/task-queues.ts
evidence:
- Pinned capability test specifications, related workflows and the scenario-specific code or suite sources.
coverage_findings:
- FND-CRM-ACT-062
---

# Task Configuration and Routing: Feature Acceptance Suite

## What the Feature Must Do as a Whole

The feature acceptance checks follow catalog maintenance into task selection and shared routing. They include the service behavior of inactive configuration and the consequences for available queue views.

## Interactions Between Capabilities

Classification and queue records are tested through the work that references them. The feature has one owned capability; its interaction cases cross into task entry, routing and discovery.

## Regression Record

| Revision | Change | Scenario | Why |
|---|---|---|---|
| 1 | initial | all | Establish cumulative acceptance across the feature and its related capabilities. |