Rhythm 2.0 Specifications

Appearance

JNY-CRM-DQ-002An administrator combines a sparse contact with a member record

Markdown

JNY-CRM-DQ-002

An administrator combines a sparse contact with a member record

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

Planning

Feature
FEAT-CRM-DQ-04
Actor
ACT-CRM-009
Capabilities
CAP-CRM-DQ-010, CAP-CRM-DQ-012, CAP-CRM-DQ-013, CAP-CRM-DQ-014, CAP-CRM-DQ-015, CAP-CRM-DQ-016, CAP-CRM-DQ-018, CAP-CRM-DQ-019
Rules in play
BR-CAP-CRM-DQ-010-06, BR-CAP-CRM-DQ-012-03, BR-CAP-CRM-DQ-013-05, BR-CAP-CRM-DQ-014-01, BR-CAP-CRM-DQ-014-14, BR-CAP-CRM-DQ-015-03, BR-CAP-CRM-DQ-016-02, BR-CAP-CRM-DQ-016-06, BR-CAP-CRM-DQ-018-01, BR-CAP-CRM-DQ-019-04

KindJourneyProduct areaCRMModuleDuplicate Review and Record MergingRevision1End-to-endRequired

Read atreact-console baf6dae3services-crm a8d1364f

An administrator combines a sparse contact with a member record ​

Story ​

An administrator investigating a member selects an event-created duplicate from the page indicator. They inspect the survivor recommendation and retain the appropriate member identity. After choosing the sparse record's job title, they review consent and other automatic outcomes, the related work and all omissions. They confirm and follow the job. The old record link and retained merge outcome then let them check where the sparse record went and what the survivor received.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Goal
Combine the member records, inspect retained information and verify the completed result.
Screens
/console/{tenantId}/crm/contacts/{id}/console/{tenantId}/crm/merges/new/console/{tenantId}/crm/merges/plans/{planId}/console/{tenantId}/crm/dataQuality/merges/{mergeId}

Steps

#SurfaceActionCapabilityExpectedProvenance
1/console/{tenantId}/crm/contacts/{id}Expand duplicate suggestions, select the sparse contact and launch Merge With Selected.CAP-CRM-DQ-010Both records enter the workspace without forcing the current record to survive.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
2createMergePlanInspect the new preview.CAP-CRM-DQ-012Participant summaries, survivor reasoning and outstanding choices are visible.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0248.spec.ts#CRM-ACC-0248
3updateMergePlanChoose the sparse contact's title and retain the member's e-mails.CAP-CRM-DQ-013The plan retains each answer and recomputes its result.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0249.spec.ts#CRM-ACC-0249
4/console/{tenantId}/crm/merges/plans/{planId}Inspect automatic combinations and discarded values, then acknowledge them.CAP-CRM-DQ-014The preview shows restricted consent, the filled birth date and reasons for omissions.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0254.spec.ts#CRM-ACC-0254
5/console/{tenantId}/crm/merges/plans/{planId}Review the related-work actions.CAP-CRM-DQ-015Readable counts describe tasks and activities moving to the survivor.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0258.spec.ts#CRM-ACC-0258
6executeMergePlanConfirm the two-contact merge.CAP-CRM-DQ-016The monitored job completes successfully.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0253.spec.ts#CRM-ACC-0253
7/console/{tenantId}/crm/contacts/{id}Follow the sparse contact's earlier link.CAP-CRM-DQ-018The survivor page explains the move using both record numbers.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0253.spec.ts#CRM-ACC-0253
8/console/{tenantId}/crm/dataQuality/merges/{mergeId}Open the outcome from the completion message and history.CAP-CRM-DQ-019Attribution and retained, moved and discarded information are available.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0253.spec.ts#CRM-ACC-0253

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate3The administrator keeps all recommendations.Confirm acceptance of defaults.The survivor uses recommended values and the outcome identifies defaults.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0254.spec.ts#CRM-ACC-0254
alternate1No detected pair connects the records.Select Merge from the record and choose its counterpart.The chosen records open in the same merge workspace.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
failure6A participant is locked.The preview prevents confirmation and explains the block.Record information remains unchanged.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0265.spec.ts#CRM-ACC-0265
failure6Ordinary survivor validation rejects a planned value.Execution identifies the field and reopens the plan.The transaction leaves all participants unchanged.test
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0265.spec.ts#CRM-ACC-0265

Assertions

IdStatementProvenance
01Absorbed record routes identify their survivor, while a never-held identity still returns not found.test
services-crm:modules/merges/tests/e2e/merged-records.e2e.spec.js#still answers 404 for an id nothing was merged under
02The permanent outcome retains selected decisions alongside original participant values.test
services-crm:modules/merges/tests/e2e/merges.e2e.spec.js#carries the decision that was made in the merge’s own record, so what was chosen is evidence
03Repeated confirmation returns the existing merge instead of another combination.test
services-crm:modules/merges/tests/e2e/merges.e2e.spec.js#answers the same merge to a second execution request, rather than merging twice

End-to-end policy: required: This flow crosses record-page selection, decision review, acknowledgement, job monitoring and history, including browser-specific old-link navigation.

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