Rhythm 2.0 Specifications

Appearance

FAS-CRM-ACT-01Interaction Records and Timelines: Feature Acceptance Suite

Markdown

FAS-CRM-ACT-01

Interaction Records and Timelines: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ACT-01
Capabilities
CAP-CRM-ACT-001, CAP-CRM-ACT-002, CAP-CRM-ACT-003, CAP-CRM-ACT-004, CAP-CRM-ACT-005, CAP-CRM-ACT-006, CAP-CRM-ACT-007
Executed by
TST-CRM-ACT-006, TST-CRM-ACT-034, TST-CRM-ACT-035, TST-CRM-ACT-059

Product areaCRMModuleActivities, Follow-ups and Task WorkRevision1

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

Interaction Records and Timelines: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The feature acceptance checks follow shared interactions from entry to discovery, correction and retained history. Supporting files and follow-up work are checked where they meet the interaction record.

Interactions Between Capabilities ​

A changed interaction affects several timelines, its revisions and any retained files. Initial follow-up creation adds ordinary task work, so acceptance checks compare both records and their read surfaces.

Regression Record ​

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

Scenarios

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

01 Record one meeting in every related context behaviour test
Exercises
CAP-CRM-ACT-001 CAP-CRM-ACT-005
Relies on
ATS-CRM-ACT-001-02 ATS-CRM-ACT-005-04
Preconditions
A coordinator has two contacts and an organization with no prior interaction.
Steps
[object Object], [object Object]
Expected
Each context contains one meeting with the same record identity and a single summary contribution.
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-0690.spec.ts
02 Turn a shared meeting into visible follow-up work interaction test
Exercises
CAP-CRM-ACT-001 CAP-CRM-ACT-002 CAP-CRM-ACT-005 CAP-CRM-ACT-010 CAP-CRM-ACT-014
Relies on
ATS-CRM-ACT-002-03 ATS-CRM-ACT-005-04
Preconditions
The activity type suggests follow-up work and the coordinator can create tasks.
Steps
[object Object], [object Object]
Expected
One meeting and one related task exist; the timeline and task view identify the same follow-up.
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-0690.spec.ts
03 Correct and remove an entry while retaining its history lifecycle test
Exercises
CAP-CRM-ACT-003 CAP-CRM-ACT-005 CAP-CRM-ACT-006
Relies on
ATS-CRM-ACT-003-04 ATS-CRM-ACT-003-07 ATS-CRM-ACT-006-02
Preconditions
An unlocked interaction links a contact and an organization.
Steps
[object Object], [object Object], [object Object]
Expected
The correction updates the remaining timeline contexts; the live entry is absent after deletion and its attributed deletion revision remains.
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-0691.spec.ts
04 Read relationship context without gaining write controls permissionnegative test
Exercises
CAP-CRM-ACT-001 CAP-CRM-ACT-003 CAP-CRM-ACT-005 CAP-CRM-ACT-006
Relies on
ATS-CRM-ACT-005-01 ATS-CRM-ACT-006-01
Preconditions
Reader, administrator and no-access personas inspect the same interaction.
Steps
[object Object], [object Object]
Expected
Allowed reads remain available; reader mutations are forbidden and corresponding console controls are absent.
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-0715.spec.ts
05 Repeat a meeting save without duplicating its follow-up regression test
Exercises
CAP-CRM-ACT-001 CAP-CRM-ACT-002
Relies on
ATS-CRM-ACT-001-11 ATS-CRM-ACT-002-06
Preconditions
A client-selected time-ordered identifier accompanies an activity with a follow-up.
Steps
[object Object], [object Object]
Expected
Identical deliveries return the same activity and retain one task; changed content under the identifier conflicts.
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/activities.create-retries.integration.spec.js
06 Keep files aligned with correction and history interaction proposed
Exercises
CAP-CRM-ACT-001 CAP-CRM-ACT-003 CAP-CRM-ACT-004 CAP-CRM-ACT-006
Relies on
ATS-CRM-ACT-004-02 ATS-CRM-ACT-004-03 ATS-CRM-ACT-006-02
Preconditions
An activity has two prepared file references.
Steps
[object Object], [object Object]
Expected
Retained files and revision sections reflect the corrections; deletion releases remaining references through shared cleanup.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/activities/services/persistence/activities.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