ATS-CRM-REG-002 Retire regions while preserving their references: Capability Test Specification
Markdown Design / CRM / Regions / Regional Catalogue / Capability Test Specification Retire regions while preserving their references: 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.
Retirement affects policy currency without disabling matching. The interaction scenario connects maintain the region catalogue, determine an address’s geographic region, identify placements that need recalculation with this capability. Cross-workflow expectations are proposed where no executable binding is present.
Show evidence (sources, provenance, origins, pinned commits)Coverage Rule gap: FND-CRM-REG-047 Transition covered Validation gap: FND-CRM-REG-047 Permission covered Edge covered Failure gap: FND-CRM-REG-047 Boundary gap: FND-CRM-REG-047 Concurrency gap: FND-CRM-REG-047 Invariant covered Interaction covered Test Scenarios 8 scenarios proving CAP-CRM-REG-002 ; 4 bound to an existing test.
03 Delete authority is separate from edit authority permission browser negative test
Proves BR-CAP-CRM-REG-002-03 Preconditions A user can create and update regions but cannot delete them. Steps Request removal through the service and inspect the region menu. Expected Deletion requires the delete key and the menu supplies no usable Delete action. Data An ordinary user-tier identity. Bound to Source services-crm:tests/unit/regions-authorization.spec.ts #requires crm.regions.delete to delete a region 04 Ordinary replacement can alter a delete lock edge api negative proposed
Proves BR-CAP-CRM-REG-002-04 Preconditions One region has a delete lock and another has a full lock. Steps Delete the first, replace the second and replace the first without its lock. Expected Deletion and the full-lock update are refused; the ordinary replacement clears the delete lock. Data Regional examples with deletion and full locks. Source services-crm:modules/regions/services/persistence/regions.ts:updateRegionRow, deleteRegionRow 05 Deactivation distinguishes referenced targets transition api proposed
Proves BR-CAP-CRM-REG-002-07 Preconditions Assignment is enabled and the current generation has a successful run. Steps Deactivate a target of an enabled rule and read settings; repeat with an unreferenced region. Expected The referenced target raises recalculation need and the unrelated deactivation records no policy change. Data A pair of regional definitions and one policy entry. Source FND-CRM-REG-021 07 Retirement affects policy currency without disabling matching interaction api proposed
Proves BR-CAP-CRM-REG-002-07 BR-CAP-CRM-REG-002-08 BR-CAP-CRM-REG-006-01 BR-CAP-CRM-REG-010-03 Preconditions A region has an enabled rule and a current successful recalculation. Steps Retire the definition through catalogue editing, read policy currency, then preview a matching address. Expected The region remains readable, recalculation is outstanding and the enabled rule still supplies the retired target. Data A region has an enabled rule and a current successful recalculation. Source WF-CRM-REG-004 08 Retired definitions can return to use without another policy stamp transition api proposed
Proves BR-CAP-CRM-REG-002-02 BR-CAP-CRM-REG-002-06 BR-CAP-CRM-REG-002-07 Preconditions An unused inactive definition and an active definition referenced by an enabled rule exist. Steps Edit the inactive definition while retaining retirement, reactivate it, retire the referenced definition, then clear its dependencies and delete it. Expected Reads show each availability change; reactivation leaves generation unchanged and removal becomes possible only after dependencies are gone. Data An unused inactive definition and an active definition referenced by an enabled rule exist. Source STATE-CRM-REG-001 ← Previous Capability Test Specification ATS-CRM-REG-001 · Maintain the region catalogue: Capability Test Specification Next Capability Test Specification → ATS-CRM-REG-003 · Configure automatic placement and its address sources: Capability Test Specification