Skip to content

JNY-CRM-REG-002An administrator applies revised coverage to existing records

Markdown

JNY-CRM-REG-002

An administrator applies revised coverage to existing records

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindJourneyProduct areaCRMModuleRegionsRevision2End-to-endRequired

Read atservices-crm a8d1364freact-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Goal
Apply revised chapter coverage while preserving deliberate record exceptions.
Screens
/console/{tenantId}/configuration/crm/regions/assignmentRules/console/{tenantId}/configuration/crm/regions?tab=rules

Steps

#SurfaceActionCapabilityExpectedProvenance
1/console/{tenantId}/configuration/crm/regions/assignmentRulesChange New York coverage to the second region and save the policy.CAP-CRM-REG-004The new coverage is stored without updating existing placements.test
2/console/{tenantId}/configuration/crm/regions?tab=rulesVisit the saved Assignment Rules tab.CAP-CRM-REG-010The need banner provides the recalculation action.test
react-console:e2e/dev/regions.dev.spec.ts#asks for a recalculation after a rule changes, and stops asking once it has run
3/console/{tenantId}/configuration/crm/regions?tab=rulesStart recalculation from the banner.CAP-CRM-REG-011The view displays processing progress in place of the need notice.test
react-console:components/regions/__tests__/recalculation.test.tsx#the banner › shows the progress of a run in its place, without a second button
4getRegionRecalculationInspect the completed run record.CAP-CRM-REG-012The result identifies completion and the examined and changed counts.test
5/console/{tenantId}/crm/contacts/{id}Read the placements of an eligible New York member, an overridden member and a never-addressed member.CAP-CRM-REG-011The eligible member moves, while the two exceptions retain their placements.test
6/console/{tenantId}/configuration/crm/regions?tab=rulesReturn to the policy view after completion.CAP-CRM-REG-010A successful run covering the current generation clears the need signal.test
react-console:e2e/dev/regions.dev.spec.ts#asks for a recalculation after a rule changes, and stops asking once it has run

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate3Another start is requested while processing remains active.The request returns the existing running record.The workspace retains one active run.test
alternate3Policy changes before the run completes.Later batches read the changed coverage.Completion still leaves another recalculation needed.test
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule saved while a recalculation is under way › says one is still needed, because the run was recorded under the rules as they were before
failure3A batch cannot finish.The run retains a redacted reason and resumes on later delivery.It recovers or becomes failed on final unsuccessful delivery, permitting a new run.test
services-crm:modules/regions/tests/integration/services/region-assignment/region-recalculation-errors.integration.spec.js#the last delivery of a run’s event › fails the run, because nothing will deliver its event again

Assertions

IdStatementProvenance
01Eligible addressed records receive the updated policy’s result.test
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#rule changes and the recalculation › moves a contact to its region under the new rules
02Overrides and records without a past or present deciding address preserve placement.test
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#rule changes and the recalculation › leaves a contact that overrides automatic assignment
03Repeating the run without changed inputs does not alter placement.test
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#rule changes and the recalculation › changes nothing on a second run under the same rules

End-to-end policy: required: Starting, watching and completing background work involve console states that require browser coverage.

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.