Rhythm 2.0 Specifications

Appearance

ATS-PFM-INT-022Acceptance for customer business calendars

Markdown

ATS-PFM-INT-022

Acceptance for customer business calendars

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-INT-022

Design

Executed by
TST-PFM-INT-002, TST-PFM-INT-588, TST-PFM-INT-590, TST-PFM-INT-596

KindAcceptance test setProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision3

Read atservices-platform ad3f6a65macroservice-libraries 54536a44react-console baf6dae3

Schedule work using customer business calendars: Capability Test Specification ​

Coverage ​

RuleProved By
BR-CAP-PFM-INT-022-01ATS-PFM-INT-022-01
BR-CAP-PFM-INT-022-02ATS-PFM-INT-022-02, ATS-PFM-INT-022-07
BR-CAP-PFM-INT-022-03ATS-PFM-INT-022-03
BR-CAP-PFM-INT-022-04ATS-PFM-INT-022-06
BR-CAP-PFM-INT-022-05ATS-PFM-INT-022-04
BR-CAP-PFM-INT-022-06ATS-PFM-INT-022-05

Calendar configuration feeds calculations performed by a workflow host. The interaction cases distinguish existing timers from later calculations and follow workspace provisioning and deletion across calendar and integration records.

The structured scenarios name the capabilities and rules involved. A bound test contributes only the outcomes it asserts; proposed transition matrices and composed interactions still require executable proof.

Coverage

  • Rule gap: FND-PFM-INT-094
  • Transition covered
  • Validation covered
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-INT-094
  • Boundary covered
  • Concurrency gap: FND-PFM-INT-094
  • Invariant gap: FND-PFM-INT-094
  • Interaction covered

Test Scenarios

7 scenarios proving CAP-PFM-INT-022; 3 bound to an existing test.

01 Calendar validation preserves the single-default choicevalidationapinegativetest
Proves
BR-CAP-PFM-INT-022-01
Preconditions
A workspace already has a default.
Steps
Create invalid zones, empty weekdays, reversed hours and four hundred and one holidays, then a valid new default.
Expected
Invalid calendars refuse; the accepted default clears the previous flag.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses more than 400 holidays
02 Provisioning seeds the working week oncetransitionapitest
Proves
BR-CAP-PFM-INT-022-02
Preconditions
A workspace has not yet received defaults.
Steps
Provision, remove Standard week and provision again.
Expected
The initial seed is default and its later user deletion does not cause recreation.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/workflow-actions/tests/integration/services/maintenance/tenant-participant.integration.spec.js#gives the tenant Standard week in its own zone, as its default
03 Business arithmetic follows local working timeedgeunittest
Proves
BR-CAP-PFM-INT-022-03
Preconditions
A Monday-to-Friday calendar has a Monday holiday and nine-to-five hours.
Steps
Add two business days to Friday at four and four business hours from three.
Expected
The results are Wednesday at four and the next working day at eleven, respectively.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
macroservice-libraries:packages/workflow-actions/src/business-days.spec.ts#P2D business from a Friday 16:00 with a Monday holiday lands on Wednesday 16:00, across the DST change (08 §10 case 8)
04 Configuration mutation requires the matching authoritypermissionapinegativeproposed
Proves
BR-CAP-PFM-INT-022-05
Preconditions
A caller has registry read alone.
Steps
Attempt creation of a business calendar.
Expected
The creation request is denied without its management permission.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Source
services-platform:modules/workflow-actions/aws/api/workflow-actions.routes.ts:workflowActionsRoutes
05 Calendar limits and locks preserve existing stateboundaryapinegativeproposed
Proves
BR-CAP-PFM-INT-022-06
Preconditions
The workspace holds one hundred calendars, an old copy, locked entries and one unlocked default.
Steps
Exceed the count, replace the old copy, mutate locked entries and delete the unlocked default.
Expected
Count, concurrency and lock violations preserve records and default; permitted default deletion leaves no default.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Source
services-platform:modules/workflow-actions/services/persistence/business-calendars.ts:createBusinessCalendar
06 Calendar edits leave an already scheduled timer unchangedinteractionapiproposed
Proves
BR-CAP-PFM-INT-020-07 BR-CAP-PFM-INT-022-04
Preconditions
A host has a business-duration timer calculated from its workspace calendar.
Steps
Change the calendar and inspect the shared timer view before calculating a new timer.
Expected
The existing timer retains its due date and the new calculation uses the changed calendar.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/workflow-actions/tests/integration/services/persistence/cross-workflow-views.queries.integration.spec.js#skips a host with no view, and one whose view lacks a column, naming each,services-platform:docs/workflow-actions/README.md#How a host reads a calendar
07 Workspace lifecycle separates defaults from retained historyinteractionapiproposed
Proves
BR-CAP-PFM-INT-003-11 BR-CAP-PFM-INT-022-02
Preconditions
Two workspaces have installations and seeded calendars.
Steps
Retry provisioning, delete one workspace through its participants and inspect the remaining workspace.
Expected
Provisioning creates no duplicate seed and deletion removes only the selected workspace records, with protected history removed last.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/maintenance/tenant-participant.integration.spec.js#leaves every table of the module empty of the tenant, the ones the application can delete included,services-platform:modules/workflow-actions/tests/integration/services/maintenance/tenant-participant.integration.spec.js#gives the tenant Standard week in its own zone, as its default

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