Rhythm 2.0 Specifications

Appearance

FAS-PFM-MTD-06Linked Records Acceptance

Markdown

FAS-PFM-MTD-06

Linked Records Acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-MTD-06
Capabilities
CAP-PFM-MTD-017, CAP-PFM-MTD-018, CAP-PFM-MTD-019
Executed by
TST-PFM-MTD-017, TST-PFM-MTD-020, TST-PFM-MTD-023, TST-PFM-MTD-025, TST-PFM-MTD-026

Product areaPlatformModuleMetadata and Organization-defined RecordsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Linked Records: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The suite follows linked records 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 ​

Merge changes links and reference values to the same survivor. 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-06 as a whole.

01 Staff maintain a crew connection from either endpoint behaviour test
Exercises
CAP-PFM-MTD-017 CAP-PFM-MTD-018
Relies on
ATS-PFM-MTD-017-02 ATS-PFM-MTD-018-10
Preconditions
A crew type links Contacts and Boat.
Steps
[object Object]
Expected
Both pages show the connection using their directional labels.
Data
A crew type links Contacts and Boat.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M6-S03.spec.ts#PLAT-M6-S03: a registrar adds Tom as crew of Osprey and Tom's page lists Osprey after a refresh
02 Merge changes links and reference values to the same survivor interaction test
Exercises
CAP-PFM-MTD-018 CAP-PFM-MTD-019
Relies on
ATS-PFM-MTD-019-07 ATS-PFM-MTD-019-08 ATS-PFM-MTD-018-10
Preconditions
Jane and her duplicate have crew links, owned boats and a Previous Owner reference.
Steps
[object Object]
Expected
All surviving connections and the reference identify the surviving Jane.
Data
Jane and her duplicate have crew links, owned boats and a Previous Owner reference.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M6-S11.spec.ts#PLAT-M6-S11: after CRM merges Jane's duplicate her crew places, her boats and Osprey's Previous Owner name the surviving Jane
03 A used relationship type retires and returns without losing links lifecycle test
Exercises
CAP-PFM-MTD-017 CAP-PFM-MTD-018
Relies on
ATS-PFM-MTD-017-05 ATS-PFM-MTD-017-06
Preconditions
A used type exists and Boat has a separate owner type.
Steps
[object Object]
Expected
The used type returns, the unused type disappears and the owner dependency prevents retirement.
Data
A used type exists and Boat has a separate owner type.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M6-S09.spec.ts#PLAT-M6-S09: a relationship type is relabelled, retired, revived and removed, and Boat's owner type cannot be retired
04 Link maintenance and type administration use different grants permissionnegative test
Exercises
CAP-PFM-MTD-017 CAP-PFM-MTD-018
Relies on
ATS-PFM-MTD-017-08 ATS-PFM-MTD-018-11
Preconditions
Standard and read-only staff have access to the endpoint records.
Steps
[object Object]
Expected
Standard staff can link, end and remove; neither ordinary tier receives type administration and readers receive no maintenance actions.
Data
Standard and read-only staff have access to the endpoint records.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M6-S12.spec.ts#PLAT-M6-S12: a standard user links, ends and removes but has no Relationship Types screen, and a read-only colleague sees no actions
05 A future end date still protects a booked place regressionnegative test
Exercises
CAP-PFM-MTD-017 CAP-PFM-MTD-018
Relies on
ATS-PFM-MTD-018-02 ATS-PFM-MTD-018-03
Preconditions
Osprey has a charter ending next month.
Steps
[object Object]
Expected
The refusal names the existing charter and the second connection is not saved.
Data
Osprey has a charter ending next month.
Bound to
Source
react-console:acceptance/custom-objects/playwright/journeys/PLAT-M6-S06.spec.ts#PLAT-M6-S06: a charter ending next month still holds Osprey and a second charter from today is refused naming the first

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