Rhythm 2.0 Specifications

Appearance

ATS-ACC-CLS-016Include close history in data export and erasure: Capability Test Specification

Markdown

ATS-ACC-CLS-016

Include close history in data export and erasure: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-ACC-CLS-016

Design

Executed by
TST-ACC-CLS-048

KindAcceptance test setProduct areaAccountingModuleMonth-End ClosingRevision2

Read atservices-accounting f47cb263

Include close history in data export and erasure: Capability Test Specification ​

Coverage ​

Coverage records the cases specified here. Proposed cases and remaining variants need executable proof before qualification.

RuleScenarios or Finding
BR-CAP-ACC-CLS-016-01ATS-ACC-CLS-016-01, ATS-ACC-CLS-016-03
BR-CAP-ACC-CLS-016-02ATS-ACC-CLS-016-01, ATS-ACC-CLS-016-03
BR-CAP-ACC-CLS-016-03ATS-ACC-CLS-016-01, ATS-ACC-CLS-016-03
BR-CAP-ACC-CLS-016-04ATS-ACC-CLS-016-02, ATS-ACC-CLS-016-03, ATS-ACC-CLS-016-04
BR-CAP-ACC-CLS-016-05ATS-ACC-CLS-016-02, ATS-ACC-CLS-016-03, ATS-ACC-CLS-016-04

Export retained history before ordered erasure. Read and export the selected workspace’s records, erase its close history, then attempt to read those records and inspect the other workspace. Export includes the selected captured history before erasure; ordered removal clears its records and preserves the other workspace’s records. The interaction scenario names related capabilities and the workflows it exercises in its structured evidence.

Coverage

  • Rule gap: FND-ACC-CLS-072
  • Transition gap: FND-ACC-CLS-072
  • Validation gap: FND-ACC-CLS-072
  • Permission not-applicable
  • Edge gap: FND-ACC-CLS-072
  • Failure covered
  • Boundary covered
  • Concurrency gap: FND-ACC-CLS-072
  • Invariant covered
  • Interaction covered

Test Scenarios

4 scenarios proving CAP-ACC-CLS-016; 1 bound to an existing test.

01 Export retained customer historyboundaryapiproposed
Proves
BR-CAP-ACC-CLS-016-01 BR-CAP-ACC-CLS-016-02 BR-CAP-ACC-CLS-016-03
Preconditions
Close and reopen runs straddle the export cutoff.
Steps
Export the fiscal-close dataset.
Expected
Eligible runs include captured snapshots, omit operational jobs and retry keys, and exclude later creations.
Data
History with snapshots and a post-cutoff run.
Source
services-accounting:modules/fiscal-close/export/fiscal-close.dataset.ts:fiscalCloseExport
02 Erase history in dependency orderinvariantapinegativetest
Proves
BR-CAP-ACC-CLS-016-04 BR-CAP-ACC-CLS-016-05 INV-DOM-ACC-CLS-004-09
Preconditions
Two workspaces contain periods, runs, jobs and snapshots.
Steps
Attempt Books removal first, then purge close history and retry Books removal.
Expected
Initial removal is refused; ordered close erasure permits later period removal and preserves the other workspace.
Data
Two workspace lifecycle fixtures.
Bound to
services-accounting:modules/maintenance/tests/integration/services/participants/fiscal-close-participant.integration.spec.js#is refused by the database when the configuration is purged before fiscal close, whose runs name its periods
services-accounting:modules/maintenance/tests/integration/services/participants/fiscal-close-participant.integration.spec.js#removes the snapshot first, then the close job, then the runs, one row a batch, and answers done
Source
services-accounting:modules/maintenance/tests/integration/services/participants/fiscal-close-participant.integration.spec.js#removes the snapshot first, then the close job, then the runs, one row a batch, and answers done
03 Export retained history before ordered erasureinteractionapiproposed
Proves
BR-CAP-ACC-CLS-016-01 BR-CAP-ACC-CLS-016-02 BR-CAP-ACC-CLS-016-03 BR-CAP-ACC-CLS-016-04 BR-CAP-ACC-CLS-016-05
Preconditions
Two workspaces each have successful closes, snapshots and reopen history.
Steps
Read and export the selected workspace’s records, erase its close history, then attempt to read those records and inspect the other workspace.
Expected
Export includes the selected captured history before erasure; ordered removal clears its records and preserves the other workspace’s records.
Data
Two workspaces each have successful closes, snapshots and reopen history.
Source
rhythm-v2-docs:specs/accounting/close/design/workflows/WF-ACC-CLS-008-erase-the-close-history-with-the-workspace.md#What It Does,services-accounting:modules/fiscal-close/export/fiscal-close.dataset.ts:fiscalCloseExport,services-accounting:modules/fiscal-close/export/fiscal-close.dataset.ts:fiscalCloseExport,services-accounting:modules/fiscal-close/export/fiscal-close.dataset.ts:fiscalCloseExport,services-accounting:modules/maintenance/tests/integration/services/participants/fiscal-close-participant.integration.spec.js#is refused by the database when the configuration is purged before fiscal close, whose runs name its periods,services-accounting:modules/maintenance/tests/integration/services/participants/fiscal-close-participant.integration.spec.js#leaves the other tenant’s rows exactly as they were
04 Resume erasure after a failed batchfailureapinegativeproposed
Proves
BR-CAP-ACC-CLS-016-04 BR-CAP-ACC-CLS-016-05
Preconditions
The selected workspace has snapshots and jobs; a later deletion batch fails after an earlier batch commits.
Steps
Retry the purge callback and inspect remaining rows in both the selected and another workspace.
Expected
Earlier deletions remain committed; retry continues dependency-ordered removal and preserves the other workspace.
Data
The selected workspace has snapshots and jobs; a later deletion batch fails after an earlier batch commits.
Source
services-accounting:modules/maintenance/services/participants/fiscal-close-participant.ts:accountingFiscalCloseParticipant

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