Rhythm 2.0 Specifications

Appearance

FAS-CRM-ACT-02Activity Classification: Feature Acceptance Suite

Markdown

FAS-CRM-ACT-02

Activity Classification: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ACT-02
Capabilities
CAP-CRM-ACT-008, CAP-CRM-ACT-009
Executed by
TST-CRM-ACT-002, TST-CRM-ACT-009, TST-CRM-ACT-068

Product areaCRMModuleActivities, Follow-ups and Task WorkRevision1

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

Activity Classification: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The feature acceptance checks connect customer configuration with baseline identity and later use. Retirement, restoration and repeated setup are checked together so catalog administration remains coherent.

Interactions Between Capabilities ​

Classification changes affect new selection and earlier correction differently. Baseline adoption is checked alongside those changes to expose accidental replacement of customer choices.

Regression Record ​

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

Scenarios

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

01 Maintain customer categories alongside protected baseline entries behaviour test
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-009
Relies on
ATS-CRM-ACT-008-02 ATS-CRM-ACT-009-03
Preconditions
An administrator has the baseline catalog and a customer-defined category.
Steps
[object Object], [object Object]
Expected
Customer configuration and valid ordering save; the built-in entry refuses deletion.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js
02 Retired baseline choices retain customer configuration interaction proposed
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-009 CAP-CRM-ACT-001 CAP-CRM-ACT-003
Relies on
ATS-CRM-ACT-008-07 ATS-CRM-ACT-009-02 ATS-CRM-ACT-003-05
Preconditions
A renamed baseline type has an existing interaction.
Steps
[object Object], [object Object]
Expected
Customer naming survives adoption; retirement blocks new selection while prior use remains correctable.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/activities/services/persistence/activity-types.ts
03 Retire and restore category and result availability lifecycle proposed
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-001 CAP-CRM-ACT-003
Relies on
ATS-CRM-ACT-008-07 ATS-CRM-ACT-001-07 ATS-CRM-ACT-003-05
Preconditions
An active customer type and outcome have existing interactions.
Steps
[object Object], [object Object]
Expected
New use follows availability and an earlier selection remains retained during correction.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/activities/services/persistence/activity-types.ts
04 Inspect configuration without maintaining it permissionnegative test
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-009
Relies on
ATS-CRM-ACT-008-01 ATS-CRM-ACT-009-01
Preconditions
A caller can read activity classifications but cannot maintain them.
Steps
[object Object]
Expected
The list is readable and creation returns Forbidden; baseline maintenance gains no exemption.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js
05 Adopt an existing baseline type without overwriting it regression test
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-009
Relies on
ATS-CRM-ACT-009-02
Preconditions
A baseline identifier already has customer-edited configuration.
Steps
[object Object], [object Object]
Expected
The seed adopts the existing entry and preserves its customer values.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js
06 Inspect provisioned catalogs and a renamed baseline entry interaction test
Exercises
CAP-CRM-ACT-008 CAP-CRM-ACT-009 CAP-CRM-ACT-016
Relies on
ATS-CRM-ACT-009-01 ATS-CRM-ACT-016-08
Preconditions
A run owns a disposable workspace and its lifecycle actions.
Steps
[object Object], [object Object]
Expected
Provisioning returns the expected activity and task catalogs with no queues; Call retains its new name after the re-seed attempt.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.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