Rhythm 2.0 Specifications

Appearance

FAS-CRM-DQ-02Review Suspected Duplicate Records: Feature Acceptance Suite

Markdown

FAS-CRM-DQ-02

Review Suspected Duplicate Records: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-DQ-02
Capabilities
CAP-CRM-DQ-007, CAP-CRM-DQ-008, CAP-CRM-DQ-009, CAP-CRM-DQ-010, CAP-CRM-DQ-011

Product areaCRMModuleDuplicate Review and Record MergingRevision1

Read atservices-crm a8d1364freact-console baf6dae3rhythm-v2-docs 61315bb0

Review Suspected Duplicate Records: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Staff need a coherent account of review work from the overview, queue and record page. Decisions must remain visible when staff switch between those entry points.

Interactions Between Capabilities ​

Group decisions change queue membership and record-page suggestions. Manual confirmation must also hand valid records to merge planning even when detection supplies no pair. Every sequence remains proposed until one executable selection asserts its full outcome. Existing capability assertions supply evidence for parts of the sequence.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish feature-level handoffs from the landed capability checks.

Scenarios

5 scenarios proving FEAT-CRM-DQ-02 as a whole.

01 Queue review exposes matching evidence and workload behaviour proposed
Exercises
CAP-CRM-DQ-007 CAP-CRM-DQ-011 CAP-CRM-DQ-002
Relies on
ATS-CRM-DQ-007-08 ATS-CRM-DQ-011-01 ATS-CRM-DQ-002-08
Preconditions
A group of comparable contacts is available to a duplicate reader.
Steps
Open the overview, enter the queue and inspect one group through its shared address.
Expected
Overview totals, group location and visible evidence agree with the referenced checks.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Source
ATS-CRM-DQ-007-08; ATS-CRM-DQ-011-01; ATS-CRM-DQ-002-08
02 Group dismissal is visible across entry points interaction proposed
Exercises
CAP-CRM-DQ-007 CAP-CRM-DQ-008 CAP-CRM-DQ-010 CAP-CRM-DQ-011
Relies on
ATS-CRM-DQ-007-04 ATS-CRM-DQ-008-03 ATS-CRM-DQ-010-01 ATS-CRM-DQ-011-01
Preconditions
A run-owned group appears in the queue and on its record pages.
Steps
Dismiss the group, inspect its record-page suggestions and overview totals, then restore the group.
Expected
Review standing and group visibility remain consistent across the affected surfaces.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Source
ATS-CRM-DQ-007-04; ATS-CRM-DQ-008-03; ATS-CRM-DQ-010-01; ATS-CRM-DQ-011-01
03 Dismissal and restoration preserve separate decisions lifecycle proposed
Exercises
CAP-CRM-DQ-008
Relies on
ATS-CRM-DQ-008-02 ATS-CRM-DQ-008-04 ATS-CRM-DQ-008-05
Preconditions
A group contains one independently dismissed pair.
Steps
Dismiss the remaining group, repeat the decision and restore the group.
Expected
Earlier attribution survives repetition and the independent dismissal survives group restoration.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Source
ATS-CRM-DQ-008-02; ATS-CRM-DQ-008-04; ATS-CRM-DQ-008-05
04 Review decisions require more authority than reading permissionnegative proposed
Exercises
CAP-CRM-DQ-007 CAP-CRM-DQ-008 CAP-CRM-DQ-009
Relies on
ATS-CRM-DQ-007-07 ATS-CRM-DQ-008-07 ATS-CRM-DQ-009-04
Preconditions
A persona has duplicate-read authority without review authority.
Steps
Open its queue, then attempt dismissal and manual confirmation.
Expected
The persona can inspect review work but cannot commit either decision.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Source
ATS-CRM-DQ-007-07; ATS-CRM-DQ-008-07; ATS-CRM-DQ-009-04
05 Missed matching can still lead to merge preparation regression proposed
Exercises
CAP-CRM-DQ-009 CAP-CRM-DQ-010 CAP-CRM-DQ-012
Relies on
ATS-CRM-DQ-009-01 ATS-CRM-DQ-010-06 ATS-CRM-DQ-012-01
Preconditions
Two valid contacts can be selected even when detection does not pair them.
Steps
Manually confirm their identity, inspect record-page choices and start a merge plan.
Expected
The same valid participants reach the merge preview without depending on automatic detection.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Source
ATS-CRM-DQ-009-01; ATS-CRM-DQ-010-06; ATS-CRM-DQ-012-01

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