ATS-CRM-REG-005 Maintain individual rules alongside the shared policy: Capability Test Specification
Markdown Design / CRM / Regions / Geographic Assignment Policy / Capability Test Specification Maintain individual rules alongside the shared policy: 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.
A single-rule edit changes matching and invalidates bulk currency. The interaction scenario connects build the geographic assignment policy, 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.
Coverage Rule covered Transition covered Validation covered Permission gap: FND-CRM-REG-050 Edge covered Failure gap: FND-CRM-REG-050 Boundary covered Concurrency covered Invariant covered Interaction covered Test Scenarios 9 scenarios proving CAP-CRM-REG-005
01 Insertion supports append and earlier placement rule api test
Proves BR-CAP-CRM-REG-005-01Preconditions Two rules occupy consecutive positions. Steps Create without a position and then create at the first position. Expected The first appends; the second precedes the others, which retain a consecutive order. Data A two-entry assignment policy. Bound to Source services-crm:modules/regions/tests/e2e/regions.e2e.spec.js #appends a created rule at the end of the order 02 Individual editing checks its version concurrency api negative proposed
Proves BR-CAP-CRM-REG-005-02Preconditions A rule has version two. Steps Replace with version one, omit the replacement version and patch with the current version test. Expected The stale and missing versions are rejected while the current patch succeeds. Data A single policy entry. Source FND-CRM-REG-022 04 Reorder requires the complete distinct set validation api negative test
Proves BR-CAP-CRM-REG-005-05Preconditions Two identified rules exist. Steps Submit incomplete, duplicate and unknown-containing orders, then the valid reversed order. Expected Invalid orders identify their problems and preserve order; the valid order reverses the sequence. Data A two-entry assignment policy. Bound to Source services-crm:modules/regions/tests/e2e/regions.e2e.spec.js #answers 400 for an order that does not name every rule of the tenant 06 Enabled assignment tolerates removal of its final rule edge api test
Proves BR-CAP-CRM-REG-005-09Preconditions The policy has one enabled rule. Steps Disable and then remove that rule. Expected The requests succeed and assignment remains enabled with no rules. Data A single policy entry. Bound to Source services-crm:modules/regions/tests/e2e/regions.e2e.spec.js #the last enabled rule while assignment is on › disables it, leaving the tenant assignment on with nothing to match 07 Rule reads cannot cross workspaces boundary api negative test
Proves BR-CAP-CRM-REG-005-11Preconditions Separate workspaces hold rules. Steps List through the other workspace and request an unknown rule. Expected No foreign rule appears and the unknown read returns not found. Data Two distinct customer workspaces. Bound to Source services-crm:modules/regions/tests/e2e/regions.e2e.spec.js #the rules, one at a time › answers none of this tenant's rules to another tenant's list 08 A single-rule edit changes matching and invalidates bulk currency interaction api proposed
Proves BR-CAP-CRM-REG-005-05BR-CAP-CRM-REG-005-06BR-CAP-CRM-REG-006-01BR-CAP-CRM-REG-010-03Preconditions An enabled policy has a completed current-generation run and two overlapping rules. Steps Read a whole-policy draft, reorder rules individually, preview the overlap, inspect need and attempt to save the old draft. Expected The reordered first match supplies the result, another recalculation is needed and the stale whole-policy save conflicts. Data An enabled policy has a completed current-generation run and two overlapping rules. Source WF-CRM-REG-004 ← Previous Capability Test Specification ATS-CRM-REG-004 · Build the geographic assignment policy: Capability Test Specification Next Capability Test Specification → ATS-CRM-REG-006 · Determine an address’s geographic region: Capability Test Specification