Rhythm 2.0 Specifications

Appearance

ATS-CRM-REG-003Configure automatic placement and its address sources: Capability Test Specification

Markdown

ATS-CRM-REG-003

Configure automatic placement and its address sources: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-REG-003

Design

Executed by
TST-CRM-REG-047, TST-CRM-REG-048, TST-CRM-REG-050, TST-CRM-REG-051, TST-CRM-REG-057, TST-CRM-REG-058, TST-CRM-REG-063

KindAcceptance test setProduct areaCRMModuleRegionsRevision3

Read atservices-crm a8d1364freact-console baf6dae3

Configure automatic placement and its address sources: 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-003-01ATS-CRM-REG-003-01
BR-CAP-CRM-REG-003-02ATS-CRM-REG-003-02
BR-CAP-CRM-REG-003-03ATS-CRM-REG-003-03
BR-CAP-CRM-REG-003-04ATS-CRM-REG-003-04, ATS-CRM-REG-003-08
BR-CAP-CRM-REG-003-05ATS-CRM-REG-003-05
BR-CAP-CRM-REG-003-08ATS-CRM-REG-003-06
BR-CAP-CRM-REG-003-09ATS-CRM-REG-003-07

Changed address choices wait for explicit bulk application. The interaction scenario connects build the geographic assignment policy, keep placements aligned with address changes, identify placements that need recalculation with this capability. Cross-workflow expectations are proposed where no executable binding is present.

Coverage

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

Test Scenarios

9 scenarios proving CAP-CRM-REG-003; 7 bound to an existing test.

01 Unsaved configuration returns defaultsedgeapitest
Proves
BR-CAP-CRM-REG-003-01
Preconditions
The workspace has never saved regional settings.
Steps
Request the assignment settings.
Expected
Assignment is disabled, both kinds are selected, preferred and Main sources apply, and no policy or recalculation need exists.
Data
A workspace without prior regional configuration.
Bound to
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#the capability › answers assignment off, the legacy defaults and no rules for a tenant that saved none
02 Assignment can start with empty coverageedgeapitest
Proves
BR-CAP-CRM-REG-003-02
Preconditions
The workspace has no rules.
Steps
Enable assignment with an empty list and create an addressed contact.
Expected
The saved switch is on but the contact receives no region.
Data
A single contact record.
Bound to
Source
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#switches assignment on with an empty rule list, and reads back on with no rules
03 Record-kind selection limits placementruleapitest
Proves
BR-CAP-CRM-REG-003-03
Preconditions
Only organizations participate and coverage includes the test address.
Steps
Create a contact and an organization using that address.
Expected
The organization is placed and the contact is skipped.
Data
A policy entry with contact and organization examples.
Bound to
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#assignment switched off › gives a contact created while only organizations are assigned no region
04 Typed sources require a typevalidationapinegativetest
Proves
BR-CAP-CRM-REG-003-04
Preconditions
Workspace address types are available.
Steps
Save a typed contact source without a type, then a preferred source with a type supplied.
Expected
The missing type fails validation and the preferred source discards the supplied type.
Data
Baseline address-purpose definitions.
Bound to
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#the capability › refuses the type setting with no contact address type id
05 Existence governs service address-type choicesboundaryapinegativetest
Proves
BR-CAP-CRM-REG-003-05
Preconditions
Billing exists but is labelled for organizations.
Steps
Save an unknown contact source type, then select Billing for contacts.
Expected
The unknown type is refused against its field and the existing Billing type is accepted.
Data
Baseline address-purpose definitions.
Bound to
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#the capability › refuses a contact address type id the tenant has no address type for
06 Versionless settings writes bypass conflict checksconcurrencyapinegativetest
Proves
BR-CAP-CRM-REG-003-08
Preconditions
Settings currently have version three.
Steps
Submit version two, then omit the version.
Expected
The older version conflicts and the versionless replacement is accepted.
Data
An existing assignment configuration.
Bound to
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#the capability › refuses a save from a stale read
07 Collected validation errors preserve the policyfailureapinegativetest
Proves
BR-CAP-CRM-REG-003-09
Preconditions
Settings retain two valid rules.
Steps
Submit an empty state criterion and a missing required address type together.
Expected
The refusal identifies both validation problems and the existing rules survive.
Data
A policy retaining two entries.
Bound to
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#the capability › leaves the saved rules as they were when a save is refused
08 Changed address choices wait for explicit bulk applicationinteractionapiproposed
Proves
BR-CAP-CRM-REG-003-04 BR-CAP-CRM-REG-004-09 BR-CAP-CRM-REG-008-05 BR-CAP-CRM-REG-010-01
Preconditions
An enabled policy places contacts by their preferred addresses and already has a successful run.
Steps
Save a typed source and its full coverage; inspect an existing contact and the need signal, then edit that contact’s newly deciding address and deliver its reaction.
Expected
Saving preserves the earlier placement and raises need; the later address reaction uses the saved source and coverage.
Data
An enabled policy places contacts by their preferred addresses and already has a successful run.
Source
WF-CRM-REG-004
09 Assignment can pause and resume with retained coveragetransitionapiproposed
Proves
BR-CAP-CRM-REG-003-07 BR-CAP-CRM-REG-010-06 BR-CAP-CRM-REG-010-03
Preconditions
An enabled current policy has saved rules.
Steps
Disable assignment, edit retained coverage, inspect currency, then enable assignment and inspect the same ordered rules.
Expected
Disabled configuration retains coverage and suppresses need; reenabling requests recalculation under the changed policy.
Data
An enabled current policy has saved rules.
Source
STATE-CRM-REG-002

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