Rhythm 2.0 Specifications

Appearance

ATS-CRM-REG-014Import a catalogue of regions: Capability Test Specification

Markdown

ATS-CRM-REG-014

Import a catalogue of regions: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-REG-014

Design

Executed by
TST-CRM-REG-023, TST-CRM-REG-067

KindAcceptance test setProduct areaCRMModuleRegionsRevision3

Read atservices-crm a8d1364freact-console baf6dae3

Import a catalogue of regions: 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-014-01ATS-CRM-REG-014-01, ATS-CRM-REG-014-04
BR-CAP-CRM-REG-014-02ATS-CRM-REG-014-02
BR-CAP-CRM-REG-014-03ATS-CRM-REG-014-03, ATS-CRM-REG-014-04, ATS-CRM-REG-014-05

Imported retirement uses catalogue and policy checks. The interaction scenario connects maintain the region catalogue, restrict regional work to authorised users with this capability. Cross-workflow expectations are proposed where no executable binding is present.

Coverage

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

Test Scenarios

5 scenarios proving CAP-CRM-REG-014; 2 bound to an existing test.

01 Bulk work requires both regional keyspermissionbrowsernegativetest
Proves
BR-CAP-CRM-REG-014-01
Preconditions
A user-tier coordinator and an administrator can attempt submission.
Steps
Submit a regional file as each persona.
Expected
The coordinator’s import requests are denied and the fully authorized submission is accepted.
Data
A short regional import input file.
Bound to
Source
services-crm:tests/unit/regions-authorization.spec.ts#the data jobs of regions, which are the configuration data-job routes under /regions › requires crm.regions.bulk AND crm.regions.update of every one of them, which the read key alone does not give
02 The hosted import surface contains twelve operationsruleunittest
Proves
BR-CAP-CRM-REG-014-02
Preconditions
The route catalogue is available.
Steps
Enumerate regional data-job operations.
Expected
The twelve declared submission, inspection and control operations are present.
Data
Published regional route metadata.
Bound to
Source
services-crm:tests/unit/regions-authorization.spec.ts#the data jobs of regions, which are the configuration data-job routes under /regions › publishes the twelve routes a job of regions has: the submission, the list, the status, the lookup by source key, the two pages, the apply, the four control actions and the revalidation of conflicts
03 Imported rows share regional validationvalidationapinegativeproposed
Proves
BR-CAP-CRM-REG-014-03
Preconditions
A file contains a valid region and rows with invalid identifier, blank name and conflicting workspace.
Steps
Submit and apply the file.
Expected
The valid row is persisted and invalid rows are rejected through the regional checks.
Data
Four import rows covering valid and refused inputs.
Source
FND-CRM-REG-021
04 Imported retirement uses catalogue and policy checksinteractionapiproposed
Proves
BR-CAP-CRM-REG-014-01 BR-CAP-CRM-REG-014-03 BR-CAP-CRM-REG-002-07
Preconditions
An enabled policy targets a region whose definition is imported for replacement.
Steps
Submit and apply a versioned retirement row with both import keys, then read the region and settings; repeat submission with read-only authority.
Expected
Authorized application persists retirement and raises need through ordinary regional persistence; read-only submission is refused.
Data
An enabled policy targets a region whose definition is imported for replacement.
Source
WF-CRM-REG-005
05 Partial import application retains earlier committed rowsfailureapinegativeproposed
Proves
BR-CAP-CRM-REG-014-03 BR-CAP-CRM-REG-014-06
Preconditions
A regional file has two valid rows and a later application failure.
Steps
Apply the file through the hosted engine and inspect its result and each row through regional reads.
Expected
Earlier committed definitions remain present and failed application has no regional compensating deletion.
Data
A regional file has two valid rows and a later application failure.
Source
WF-CRM-REG-005

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