Rhythm 2.0 Specifications

Appearance

ATS-CRM-REG-009Preserve a deliberate regional exception: Capability Test Specification

Markdown

ATS-CRM-REG-009

Preserve a deliberate regional exception: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-REG-009

Design

Executed by
TST-CRM-REG-020, TST-CRM-REG-029, TST-CRM-REG-049, TST-CRM-REG-058, TST-CRM-REG-063

KindAcceptance test setProduct areaCRMModuleRegionsRevision3

Read atservices-crm a8d1364freact-console baf6dae3

Preserve a deliberate regional exception: Capability Test Specification ​

Coverage ​

Each row links a required rule to its authored proof. A covered category records a specification; executable and remaining variant gaps stay in the finding register.

RuleProved By
BR-CAP-CRM-REG-009-01ATS-CRM-REG-009-01, ATS-CRM-REG-009-05
BR-CAP-CRM-REG-009-02ATS-CRM-REG-009-02, ATS-CRM-REG-009-06
BR-CAP-CRM-REG-009-03ATS-CRM-REG-009-03, ATS-CRM-REG-009-05, ATS-CRM-REG-009-06
BR-CAP-CRM-REG-009-05ATS-CRM-REG-009-04

A held exception survives both automatic processing paths. The interaction scenario connects keep placements aligned with address changes, apply the current policy across existing records with this capability. Cross-workflow expectations are proposed where no executable binding is present.

Coverage

  • Rule covered
  • Transition covered
  • Validation gap: FND-CRM-REG-054
  • Permission gap: FND-CRM-REG-054
  • Edge gap: FND-CRM-REG-054
  • Failure gap: FND-CRM-REG-054
  • Boundary covered
  • Concurrency gap: FND-CRM-REG-054
  • Invariant covered
  • Interaction covered

Test Scenarios

6 scenarios proving CAP-CRM-REG-009; 4 bound to an existing test.

01 Overrides preserve manual exceptionsinvariantapitest
Proves
BR-CAP-CRM-REG-009-01 AS-JNY-CRM-REG-003-01
Preconditions
A contact and organization are held in the first region.
Steps
Move their deciding addresses into the second region.
Expected
Both retain the held region.
Data
A pair of CRM records.
Bound to
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#manual regions and the override › never changes the region of a contact that overrides automatic assignment
02 Manual placement without override follows changed inputruleapitest
Proves
BR-CAP-CRM-REG-009-02
Preconditions
A contact has a manual region without an override.
Steps
Save an unrelated field, then change the deciding address.
Expected
The first save preserves placement and the address change permits reassignment.
Data
A single contact record.
Bound to
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#manual regions and the override › keeps a manual region while the deciding address is unchanged
03 Releasing an override uses the current addresstransitionapitest
Proves
BR-CAP-CRM-REG-009-03 AS-JNY-CRM-REG-003-02
Preconditions
A contact and organization moved while overridden.
Steps
Disable their overrides.
Expected
Both are reconciled against their present deciding addresses.
Data
A pair of CRM records.
Bound to
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#manual regions and the override › a contact moved while overridden, then switched back to automatic › kept the region while the override was on, so the move was left undecided
04 Foreign regions cannot be saved on recordsboundaryapinegativetest
Proves
BR-CAP-CRM-REG-009-05
Preconditions
Two workspaces contain separate regional catalogues.
Steps
Set local contact and organization regions to a foreign region.
Expected
Both saves fail and preserve the previous records.
Data
Two distinct customer workspaces.
Bound to
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#refusals › refuses a contact naming a region the tenant does not have
05 A held exception survives both automatic processing pathsinteractionapiproposed
Proves
BR-CAP-CRM-REG-009-01 BR-CAP-CRM-REG-009-03 BR-CAP-CRM-REG-011-06
Preconditions
An addressed contact has a manual region protected by an override and another geographic target.
Steps
Move the deciding address, deliver assignment, run recalculation, then release the override and deliver its reaction.
Expected
The hold preserves the manual region through both processing paths and release follows the current changed address.
Data
An addressed contact has a manual region protected by an override and another geographic target.
Source
WF-CRM-REG-001
06 Releasing an unchanged hold preserves its former selectiontransitionapiproposed
Proves
BR-CAP-CRM-REG-009-02 BR-CAP-CRM-REG-009-03
Preconditions
A contact remembers an address, then holds a different manual region without changing that address.
Steps
Release the override and deliver its reaction, then move the deciding address and deliver again.
Expected
Release keeps the value while its remembered input matches; the later changed input becomes eligible for assignment.
Data
A contact remembers an address, then holds a different manual region without changing that address.
Source
STATE-CRM-REG-003

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