Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-018Retain interactions and work through record deletion and merge: Capability Test Specification

Markdown

ATS-CRM-ACT-018

Retain interactions and work through record deletion and merge: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-018

Design

Executed by
TST-CRM-ACT-003, TST-CRM-ACT-007, TST-CRM-ACT-063, TST-CRM-ACT-064

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision3

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

Retain interactions and work through record deletion and merge: Capability Test Specification ​

Coverage ​

Category coverage counts specified proof. Unbound cases remain proposed; registered assertions do not establish a passing run.

RuleProof Scenario Or Finding
BR-CAP-CRM-ACT-018-01ATS-CRM-ACT-018-01, ATS-CRM-ACT-018-04
BR-CAP-CRM-ACT-018-02ATS-CRM-ACT-018-02
BR-CAP-CRM-ACT-018-03ATS-CRM-ACT-018-04
BR-CAP-CRM-ACT-018-04ATS-CRM-ACT-018-02
BR-CAP-CRM-ACT-018-05ATS-CRM-ACT-018-03
BR-CAP-CRM-ACT-018-06FND-CRM-ACT-064
BR-CAP-CRM-ACT-018-07ATS-CRM-ACT-018-03
BR-CAP-CRM-ACT-018-08ATS-CRM-ACT-018-03

One interaction links two contacts and a task concerns the contact selected for removal. Delete that contact and read the remaining contact timeline, activity and task.

The interaction scenario names the capabilities and rules it exercises. The coverage finding retains incomplete permission combinations and failure variants.

Coverage

  • Rule gap: FND-CRM-ACT-064
  • Transition covered
  • Validation gap: FND-CRM-ACT-064
  • Permission gap: FND-CRM-ACT-064
  • Edge covered
  • Failure gap: FND-CRM-ACT-064
  • Boundary gap: FND-CRM-ACT-064
  • Concurrency gap: FND-CRM-ACT-064
  • Invariant gap: FND-CRM-ACT-064
  • Interaction covered

Test Scenarios

4 scenarios proving CAP-CRM-ACT-018; 3 bound to an existing test.

01 Retain shared activities after related-record removaltransitionapitest
Proves
BR-CAP-CRM-ACT-018-01
Preconditions
One activity links two contacts.
Steps
Delete one contact.
Expected
The activity remains available from the other contact’s timeline.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#leaves the activity on the other records’ timelines when one linked contact is deleted
services-crm:modules/activities/tests/integration/db/activities.table.integration.spec.js#drops only its links when a linked contact is deleted, and leaves the activity
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#leaves the activity on the other records’ timelines when one linked contact is deleted
02 Inspect orphan retention and deletion audit evidenceedgebrowsernegativetest
Proves
BR-CAP-CRM-ACT-018-02 BR-CAP-CRM-ACT-018-04
Preconditions
An activity has one contact link.
Steps
Delete the contact and inspect direct read, console landing and deletion revision.
Expected
The activity has no links, its landing cannot open it, and the journey records whether removed links are represented in the audit.
Data
Each run creates and isolates the records it needs.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts#CRM-ACC-0719
03 Move and collapse references during mergeinteractionbrowsertest
Proves
BR-CAP-CRM-ACT-018-05 BR-CAP-CRM-ACT-018-07 BR-CAP-CRM-ACT-018-08
Preconditions
Contacts share a meeting and the duplicate also has independent activity and work.
Steps
Merge and inspect survivor and former-record reads.
Expected
Shared links collapse with primary preserved and tasks follow; the historical journey accepts Not Found or Gone for the old timeline.
Data
Each run creates and isolates the records it needs.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts#CRM-ACC-0720
04 Record removal leaves surviving timeline and work context intactinteractionapiproposed
Proves
BR-CAP-CRM-ACT-018-01 BR-CAP-CRM-ACT-018-03 BR-CAP-CRM-ACT-005-05 BR-CAP-CRM-ACT-010-08
Preconditions
One interaction links two contacts and a task concerns the contact selected for removal.
Steps
Delete that contact and read the remaining contact timeline, activity and task.
Expected
The remaining timeline contains the shared interaction once; the task survives without the deleted contact reference.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#leaves the activity on the other records’ timelines when one linked contact is deleted; react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts#CRM-ACC-0719; services-crm:modules/activities/tests/integration/services/persistence/activities.queries.integration.spec.js#shows the activity linked to three contacts and an organization once on each of the four timelines; services-crm:modules/tasks/tests/integration/db/tasks.table.integration.spec.js#keeps the task: the work outlives the record it was about

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