Rhythm 2.0 Specifications

Appearance

FAS-CRM-ACT-04Task Configuration and Routing: Feature Acceptance Suite

Markdown

FAS-CRM-ACT-04

Task Configuration and Routing: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ACT-04
Capabilities
CAP-CRM-ACT-016
Executed by
TST-CRM-ACT-015, TST-CRM-ACT-022

Product areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3rhythm-v2-docs 18a49edf

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 ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative acceptance across the feature and its related capabilities.

Scenarios

6 scenarios proving FEAT-CRM-ACT-04 as a whole.

01 Maintain type and queue catalogs as complete lists behaviour proposed
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
[object Object], [object Object]
Expected
Valid complete orders persist and rejected incomplete lists move no records.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
02 Inactive configuration continues supporting service work interaction proposed
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
[object Object]
Expected
The service accepts both operations; configuration inactivity does not establish a routing refusal.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/tasks/services/persistence/tasks.ts
03 Protect configuration referenced by work lifecycle proposed
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
[object Object], [object Object]
Expected
Referenced deletion conflicts; after work removal the unlocked customer configuration can be deleted.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/tasks/services/persistence/task-types.ts; services-crm:modules/tasks/services/persistence/task-queues.ts
04 Refuse maintenance without administrator authority permissionnegative test
Exercises
CAP-CRM-ACT-016
Relies on
ATS-CRM-ACT-016-01
Preconditions
A caller can only read task types.
Steps
[object Object]
Expected
The route returns Forbidden and leaves the list unchanged.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js
05 Keep customization when task seeds are repeated regression test
Exercises
CAP-CRM-ACT-016
Relies on
ATS-CRM-ACT-016-08
Preconditions
Customer values already exist under baseline task-type identifiers.
Steps
[object Object], [object Object]
Expected
Existing configuration remains unchanged instead of being replaced by seed defaults.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js
06 Queue configuration determines available views and creation context interaction proposed
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
[object Object], [object Object]
Expected
Creation retains queue context; the inactive queue view disappears while existing work retains its routing.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
react-console:components/console/tasks/definition.tsx; services-crm:modules/tasks/services/persistence/task-queues.ts

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software