--- id: FAS-CRM-DQ-02 feature: FEAT-CRM-DQ-02 product_area: crm module: data-quality revision: 1 status: proposed product_intent: proposed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 61315bb0538e230286687677da2b04b1d33f162b capabilities: - CAP-CRM-DQ-007 - CAP-CRM-DQ-008 - CAP-CRM-DQ-009 - CAP-CRM-DQ-010 - CAP-CRM-DQ-011 scenarios: - id: FAS-CRM-DQ-02-01 title: Queue review exposes matching evidence and workload kind: behaviour 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. negative: false data_needs: >- 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. bound_to: [] provenance: proposed source: ATS-CRM-DQ-007-08; ATS-CRM-DQ-011-01; ATS-CRM-DQ-002-08 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-02-02 title: Group dismissal is visible across entry points kind: interaction 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. negative: false data_needs: >- 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. bound_to: [] provenance: proposed source: ATS-CRM-DQ-007-04; ATS-CRM-DQ-008-03; ATS-CRM-DQ-010-01; ATS-CRM-DQ-011-01 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-02-03 title: Dismissal and restoration preserve separate decisions kind: lifecycle 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. negative: false data_needs: >- 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. bound_to: [] provenance: proposed source: ATS-CRM-DQ-008-02; ATS-CRM-DQ-008-04; ATS-CRM-DQ-008-05 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-02-04 title: Review decisions require more authority than reading kind: permission 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. negative: true data_needs: >- 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. bound_to: [] provenance: proposed source: ATS-CRM-DQ-007-07; ATS-CRM-DQ-008-07; ATS-CRM-DQ-009-04 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. - id: FAS-CRM-DQ-02-05 title: Missed matching can still lead to merge preparation kind: regression 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. negative: false data_needs: >- 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. bound_to: [] provenance: proposed source: ATS-CRM-DQ-009-01; ATS-CRM-DQ-010-06; ATS-CRM-DQ-012-01 execution_gap: FND-CRM-DQ-072 note: >- The capability assertions define the component evidence. No executable binding is claimed for this complete feature sequence. evidence: - provenance: documented source: FEAT-CRM-DQ-02 - provenance: proposed source: - ATS-CRM-DQ-007-08 - ATS-CRM-DQ-011-01 - ATS-CRM-DQ-002-08 - ATS-CRM-DQ-007-04 - ATS-CRM-DQ-008-03 - ATS-CRM-DQ-010-01 - ATS-CRM-DQ-011-01 - ATS-CRM-DQ-008-02 - ATS-CRM-DQ-008-04 - ATS-CRM-DQ-008-05 - ATS-CRM-DQ-007-07 - ATS-CRM-DQ-008-07 - ATS-CRM-DQ-009-04 - ATS-CRM-DQ-009-01 - ATS-CRM-DQ-010-06 - ATS-CRM-DQ-012-01 --- # 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 | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish feature-level handoffs from the landed capability checks. |