Rhythm 2.0 Specifications

Appearance

FAS-PFM-MTD-04Organization-defined Record Categories Acceptance

Markdown

FAS-PFM-MTD-04

Organization-defined Record Categories Acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-MTD-04
Capabilities
CAP-PFM-MTD-009, CAP-PFM-MTD-010, CAP-PFM-MTD-011
Executed by
TST-PFM-MTD-001, TST-PFM-MTD-008, TST-PFM-MTD-010, TST-PFM-MTD-013, TST-PFM-MTD-014

Product areaPlatformModuleMetadata and Organization-defined RecordsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Organization-defined Record Categories: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The suite follows organization-defined record categories through its customer outcomes, lifecycle actions, permission refusals and retained regression cases. Each scenario names the capabilities it exercises and the detailed outcomes it relies on. Existing executable bindings identify specific assertions, while unbound scenarios remain proposed acceptance work.

Interactions Between Capabilities ​

Object-scoped reach changes navigation and record actions together. The interaction case checks the joint outcome after configuration or record state changes, so separate capability checks cannot stand in for the complete feature result.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative feature acceptance from the landed capability and design obligations.

Scenarios

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

01 An administrator brings an owned register into navigation behaviour test
Exercises
CAP-PFM-MTD-009 CAP-PFM-MTD-010
Relies on
ATS-PFM-MTD-009-04 ATS-PFM-MTD-009-05 ATS-PFM-MTD-010-01
Preconditions
An administrator starts a new Boat definition.
Steps
[object Object]
Expected
The active register appears beneath its app with the selected owner.
Data
An administrator starts a new Boat definition.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S01.spec.ts#PLAT-M5-S01: an administrator creates Boat in a new app, owned by Contact, and Marina > Boats appears
02 Object-scoped reach changes navigation and record actions together interaction test
Exercises
CAP-PFM-MTD-009 CAP-PFM-MTD-010 CAP-PFM-MTD-011
Relies on
ATS-PFM-MTD-010-06 ATS-PFM-MTD-011-02
Preconditions
Enforcement Actions is restricted to Investigators with a scoped assignment.
Steps
[object Object]
Expected
Only the assigned investigator reaches the register and can edit its records.
Data
Enforcement Actions is restricted to Investigators with a scoped assignment.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S14.spec.ts#PLAT-M5-S14: restricted to the Investigators role and granted in Security: only investigators see and edit
03 Archiving a register hides its menu and retains old links lifecycle test
Exercises
CAP-PFM-MTD-009 CAP-PFM-MTD-010
Relies on
ATS-PFM-MTD-009-08 ATS-PFM-MTD-010-06
Preconditions
Boat is active in Marina and contains a saved boat.
Steps
[object Object]
Expected
The menu no longer lists Boat and the retained boat opens read-only.
Data
Boat is active in Marina and contains a saved boat.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S10.spec.ts#PLAT-M5-S10: archiving Boat hides it from Marina; an old link still opens the boat, read-only
04 Read-only staff receive no record administration controls permissionnegative test
Exercises
CAP-PFM-MTD-010 CAP-PFM-MTD-011
Relies on
ATS-PFM-MTD-011-07 ATS-PFM-MTD-010-06
Preconditions
A volunteer can read boats and another user has no custom-record reach.
Steps
[object Object]
Expected
The volunteer receives no edit actions and the user without reach receives no menu or card.
Data
A volunteer can read boats and another user has no custom-record reach.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S08.spec.ts#PLAT-M5-S08: a read-only volunteer is offered no edit actions; a person without access sees no menu and no card
05 A register without placement remains reachable through its owner regressionnegative test
Exercises
CAP-PFM-MTD-009 CAP-PFM-MTD-010
Relies on
ATS-PFM-MTD-010-02 ATS-PFM-MTD-009-05
Preconditions
Boat has a contact owner and no app placement.
Steps
[object Object]
Expected
No menu entry is added and the boat remains reachable from the contact.
Data
Boat has a contact owner and no app placement.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S13.spec.ts#PLAT-M5-S13: a boat placed only on contacts has no menu entry and is reached from the contact's page

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