Rhythm 2.0 Specifications

Appearance

ATS-CRM-DQ-017Combine organizations and their connections safely: Acceptance Scenarios

Markdown

ATS-CRM-DQ-017

Combine organizations and their connections safely: Acceptance Scenarios

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-DQ-017

KindAcceptance test setProduct areaCRMModuleDuplicate Review and Record MergingRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Test Scenarios

9 scenarios proving CAP-CRM-DQ-017; 7 bound to an existing test.

01 Hierarchy choices exclude cycle-producing parentsunittest
Proves
BR-CAP-CRM-DQ-017-01
Preconditions
Participants include an ancestor/descendant pair and possible outside parents.
Steps
Build their plan.
Expected
Forbidden parents are absent, removed internal links are explained and children move to the survivor.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/unit/services/planning/organization-hierarchy.spec.js#leaves the survivor with no parent, because the two become one organization
services-crm:modules/merges/tests/unit/services/planning/organization-hierarchy.spec.js#reports their reassignment to the survivor as a relationship action
Source
services-crm:modules/merges/tests/unit/services/planning/organization-hierarchy.spec.js#leaves the survivor with no parent, because the two become one organization
02 Organization domains retain distinct alternativesunittest
Proves
BR-CAP-CRM-DQ-017-02
Preconditions
Participants have different primary and alternate domains.
Steps
Plan with each primary choice.
Expected
The remaining domains form the alternate union and flags combine.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/unit/services/planning/organization-fields.spec.js#unions every other distinct domain into the alternate domain names
services-crm:modules/merges/tests/unit/services/planning/organization-fields.spec.js#moves the chosen domain into the alternates when staff choose the other one
services-crm:modules/merges/tests/unit/services/planning/organization-fields.spec.js#unions every participant’s flags rather than choosing between them
Source
services-crm:modules/merges/tests/unit/services/planning/organization-fields.spec.js#unions every other distinct domain into the alternate domain names
03 Different types require review without a blockerunittest
Proves
BR-CAP-CRM-DQ-017-03
Preconditions
Participants have different organization types.
Steps
Compute their preview.
Expected
A type choice and warning appear without blocking the merge.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/unit/services/planning/organization-decisions.spec.js#asks which type the survivor keeps and warns that they may not be duplicates at all
Source
services-crm:modules/merges/tests/unit/services/planning/organization-decisions.spec.js#asks which type the survivor keeps and warns that they may not be duplicates at all
04 Affiliations move and overlapping stays combineapitest
Proves
BR-CAP-CRM-DQ-017-04
Preconditions
One employee belongs only to the absorbed organization and another belongs to both.
Steps
Execute.
Expected
No affiliation retains the absorbed organization and the equivalent stay combines into the survivor's affiliation.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#moves the affiliation of somebody who worked only at the organization that went
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#combines the two stays of somebody who worked at both into the survivor’s own affiliation
Source
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#leaves no affiliation naming the organization that went
05 Affiliation writes enforce the ceilingunitnegativetest
Proves
BR-CAP-CRM-DQ-017-05
Preconditions
Prepare 100,000-row and 100,001-row plans plus a combination exceeding the limit.
Steps
Build the previews.
Expected
The boundary plan is allowed and both excessive variants are blocked.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/unit/services/planning/organization-decisions.spec.js#plans a merge that writes exactly 100,000 affiliation rows without a blocker
services-crm:modules/merges/tests/unit/services/planning/organization-decisions.spec.js#refuses a merge whose affiliation rows rewritten and combined away pass the ceiling, though it moves fewer
Source
services-crm:modules/merges/tests/unit/services/planning/organization-decisions.spec.js#refuses a merge of 100,001 affiliations
06 Employee links follow retained organization detailsapitest
Proves
BR-CAP-CRM-DQ-017-06
Preconditions
Prepare links to kept and discarded slots and to an affiliation that combines.
Steps
Execute the plan.
Expected
Kept links remain, discarded slots and combined affiliations redirect appropriately and every change is recorded.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#re-points a link to a record that lost its slot to the record of its type the merge kept
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#keeps a link to the record the merge kept pointing at it, now the survivor’s
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#re-points a link through an affiliation a combination deleted to the affiliation it was combined into
Source
services-crm:modules/merges/tests/integration/services/merges/organization-merge-execution.integration.spec.js#re-points a link to a record that lost its slot to the record of its type the merge kept
07 Preferred-address selection survives executionapitest
Proves
BR-CAP-CRM-DQ-017-07
Preconditions
Two organizations prefer different address types.
Steps
Execute their chosen preview.
Expected
Only the address selected by the plan remains preferred.
Data
The existing scenario setup supplies the required records.
Bound to
Source
services-crm:modules/merges/tests/integration/services/merges/organization-merge-preferred-address.integration.spec.js#carries the merge out, rather than failing on the preferred-address index
08 Any added moved affiliation invalidates approvalunitproposed
Proves
BR-CAP-CRM-DQ-017-09
Preconditions
Approve an organization plan whose dependent affiliations are identified.
Steps
Add a colliding affiliation, then separately add a non-colliding affiliation.
Expected
Both additions change the material fingerprint and require renewed approval.
Data
The existing scenario setup supplies the required records.
Source
FND-CRM-DQ-026
09 Organization combination works across the full console journeybrowserproposed
Proves
BR-CAP-CRM-DQ-017-01 BR-CAP-CRM-DQ-017-02 BR-CAP-CRM-DQ-017-04 BR-CAP-CRM-DQ-017-05 BR-CAP-CRM-DQ-017-06
Preconditions
Prepare children, employees, domains and linked details.
Steps
Merge, attempt an oversized plan and combine an ancestor with its descendant.
Expected
Domains, hierarchy, people and links follow their choices; excessive size is refused and large work warns.
Data
The existing scenario setup supplies the required records.
Source
FND-CRM-DQ-031

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