Skip to content

FAS-CRM-DQ-01Locate and Prevent Duplicate Records: Feature Acceptance Suite

Markdown

FAS-CRM-DQ-01

Locate and Prevent Duplicate Records: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Product areaCRMModuleDuplicate Review and Record MergingRevision1

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

Scenarios

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

01 Changed contact evidence reaches an explained suggestion behaviour proposed
Exercises
CAP-CRM-DQ-001 CAP-CRM-DQ-002
Relies on
ATS-CRM-DQ-001-06 ATS-CRM-DQ-002-08
Preconditions
Two run-owned contacts have comparable details and no existing pair.
Steps
Create both contacts, wait for detection, then inspect the score reasons and the visible suggestion.
Expected
The suggestion and its explanation agree with the capability 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-001-06; ATS-CRM-DQ-002-08
02 Rule edits change draft refusal and later review interaction proposed
Exercises
CAP-CRM-DQ-003 CAP-CRM-DQ-004 CAP-CRM-DQ-001
Relies on
ATS-CRM-DQ-003-09 ATS-CRM-DQ-004-04 ATS-CRM-DQ-001-08
Preconditions
A matching contact exists and an authorized administrator can change the duplicate rule.
Steps
Change the applicable rule, check a draft, attempt ordinary creation, then use an explained authorized exception and process detection.
Expected
Draft response, refusal, exception attribution and later review work 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-003-09; ATS-CRM-DQ-004-04; ATS-CRM-DQ-001-08
03 Evidence refresh preserves reviewed identity lifecycle proposed
Exercises
CAP-CRM-DQ-001 CAP-CRM-DQ-005
Relies on
ATS-CRM-DQ-001-07 ATS-CRM-DQ-001-08 ATS-CRM-DQ-005-04
Preconditions
Detected and reviewed pairs exist before a re-check.
Steps
Edit matching evidence, start the authorized re-check, deliver a window twice and inspect pair identity and progress.
Expected
Only eligible suggestions retire; reviewed identities and completed progress remain consistent.
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-001-07; ATS-CRM-DQ-001-08; ATS-CRM-DQ-005-04
04 Readers cannot change configuration or start re-checks permissionnegative proposed
Exercises
CAP-CRM-DQ-003 CAP-CRM-DQ-005
Relies on
ATS-CRM-DQ-003-08 ATS-CRM-DQ-005-01
Preconditions
A staff persona can read duplicate suggestions but lacks configuration authority.
Steps
Read suggestions, attempt a rule change and attempt a re-check start with that persona.
Expected
Reading succeeds and both administration requests are refused without saved changes.
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-003-08; ATS-CRM-DQ-005-01
05 Registration decline produces review work regression proposed
Exercises
CAP-CRM-DQ-006 CAP-CRM-DQ-001
Relies on
ATS-CRM-DQ-006-03 ATS-CRM-DQ-001-06
Preconditions
Portal registration finds an eligible existing contact.
Steps
Decline that contact, create the new registration contact and inspect the resulting duplicate pair.
Expected
The new contact and declined suggestion are linked for later staff review.
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-006-03; ATS-CRM-DQ-001-06
06 Imports produce bounded review work without delaying saves interaction proposed
Exercises
CAP-CRM-DQ-001 CAP-CRM-DQ-005
Relies on
ATS-CRM-DQ-001-11 ATS-CRM-DQ-005-03
Preconditions
An isolated import population contains known duplicate pairs.
Steps
Import the population, observe completion and inspect the resulting review groups.
Expected
Saved records and group counts agree with the fixture; timing claims remain conditional where the source test makes them conditional.
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-001-11; ATS-CRM-DQ-005-03

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.