Skip to content

FAS-PFM-TNL-04Initial Import Recovery acceptance

Markdown

FAS-PFM-TNL-04

Initial Import Recovery acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Product areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-platform ad3f6a65services-crm a8d1364fservices-commerce c8b66a98services-committees 36129c24services-membership 5994c270services-submissions 64236c19services-websites 5fc6823cservices-marketing d071a159rhythm-v2-docs d318a948

Scenarios

5 scenarios proving FEAT-PFM-TNL-04 as a whole.

01 Staff correct an initial import before approving opening behaviour proposed
Exercises
CAP-PFM-TNL-011 CAP-PFM-TNL-012
Relies on
ATS-PFM-TNL-011-03 ATS-PFM-TNL-012-06 ATS-PFM-TNL-012-08 ATS-PFM-TNL-011-05
Preconditions
An active implementation workspace contains an initial import that needs correction.
Steps
Open loading, reset classified import data, inspect retained setup and reset progress, reload and activate.
Expected
Reset leaves loading available for another import; activation later restores active lifecycle without changing implementation status or removing load history.
Data
Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture records named by the relied-on capability scenarios. Use controlled clocks and faults only where the scenario requires them.
Source
rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md; rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-012-empty-a-loading-workspace-so-it-can-be-loaded-again.md
02 Activation between reset batches stops further removal interactionnegative proposed
Exercises
CAP-PFM-TNL-011 CAP-PFM-TNL-012
Relies on
ATS-PFM-TNL-011-05 ATS-PFM-TNL-012-02
Preconditions
A loading workspace has an open reset paused after a committed batch.
Steps
Activate it through the separate activation permission and resume the next reset batch.
Expected
The activation can succeed; the next batch refuses the changed lifecycle and previously committed removal remains.
Data
Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture records named by the relied-on capability scenarios. Use controlled clocks and faults only where the scenario requires them.
Source
rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md; rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-012-empty-a-loading-workspace-so-it-can-be-loaded-again.md
03 A new reset finishes the removal left by a settled failure lifecycle proposed
Exercises
CAP-PFM-TNL-011 CAP-PFM-TNL-012
Relies on
ATS-PFM-TNL-011-03 ATS-PFM-TNL-012-09
Preconditions
The loading workspace has a settled failed reset and selected rows remain.
Steps
Request another reset, follow its progress and inspect the remaining selected and retained data.
Expected
The new job finishes classified removal, keeps preserved setup and leaves the workspace loading for correction.
Data
Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture records named by the relied-on capability scenarios. Use controlled clocks and faults only where the scenario requires them.
Source
rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md; rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-012-empty-a-loading-workspace-so-it-can-be-loaded-again.md
04 Import and activation authority remain separate permissionnegative proposed
Exercises
CAP-PFM-TNL-011 CAP-PFM-TNL-012
Relies on
ATS-PFM-TNL-011-01 ATS-PFM-TNL-011-04 ATS-PFM-TNL-012-01
Preconditions
One staff caller can import and another can activate; a customer administrator has neither staff authority.
Steps
Try load entry and reset with the activation-only caller, try activation with the import-only caller and repeat the actions with customer authority.
Expected
Every cross-permission and customer attempt refuses without partial loading, activation or reset changes.
Data
Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture records named by the relied-on capability scenarios. Use controlled clocks and faults only where the scenario requires them.
Source
rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md; rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-012-empty-a-loading-workspace-so-it-can-be-loaded-again.md
05 Unsupported remote reset is refused before local records are removed regressionnegative proposed
Exercises
CAP-PFM-TNL-011 CAP-PFM-TNL-012
Relies on
ATS-PFM-TNL-011-03 ATS-PFM-TNL-012-05
Preconditions
A loading fixture has local data and a selected remote participant that does not advertise reset support.
Steps
Confirm reset for the correct workspace and inspect planning, job rows and resource counts after refusal.
Expected
Planning identifies the unsupported application, creates no reset job and removes no local or remote records.
Data
Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture records named by the relied-on capability scenarios. Use controlled clocks and faults only where the scenario requires them.
Source
rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md; rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-012-empty-a-loading-workspace-so-it-can-be-loaded-again.md

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.