Rhythm 2.0 Specifications

Appearance

FAS-PFM-NOT-03Personal Notification Workspace

Markdown

FAS-PFM-NOT-03

Personal Notification Workspace

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-NOT-03
Capabilities
CAP-PFM-NOT-009, CAP-PFM-NOT-010, CAP-PFM-NOT-014
Executed by
TST-PFM-NOT-001, TST-PFM-NOT-002, TST-PFM-NOT-008

Product areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Personal Notification Workspace: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

This suite follows the feature from its initial inputs through the outcomes people inspect. Its cases combine capability results so that a change at one stage is checked against the later stages that depend on it.

Interactions Between Capabilities ​

End the first assignment and inspect both notices and unread results. The ended scope becomes inapplicable while the other notice remains unread and applicable.

The feature cases retain their prerequisite scenario references. A component test alone does not establish execution of the complete feature chain.

Regression Record ​

RevisionChangeScenarioWhy
1initialAll initial casesEstablish cumulative feature coverage and preserve its dependencies for later revisions.

Scenarios

5 scenarios proving FEAT-PFM-NOT-03 as a whole.

01 An assignment is actionable and understandable behaviour proposed
Exercises
CAP-PFM-NOT-014 CAP-PFM-NOT-009 CAP-PFM-NOT-010
Relies on
ATS-PFM-NOT-014-01 ATS-PFM-NOT-009-08 ATS-PFM-NOT-010-06
Preconditions
Jane holds the receiving role and has authority for the responsibility destination.
Steps
Assign the responsibility, open the notice and inspect its selection explanation.
Expected
Jane reaches her responsibility and sees the producer explanation; opening updates the personal read state.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-01,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-08,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-010-understand-why-i-was-told.md#ATS-PFM-NOT-010-06
02 Ending one scope leaves another scope available interaction proposed
Exercises
CAP-PFM-NOT-014 CAP-PFM-NOT-005 CAP-PFM-NOT-009
Relies on
ATS-PFM-NOT-014-03 ATS-PFM-NOT-005-03 ATS-PFM-NOT-009-04
Preconditions
Jane receives assignment notices for two resource scopes.
Steps
End the first assignment and inspect both notices and unread results.
Expected
The ended scope becomes inapplicable while the other notice remains unread and applicable.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-03,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-03,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-04
03 Assignment ending preserves delivered history lifecycle test
Exercises
CAP-PFM-NOT-014 CAP-PFM-NOT-009
Relies on
ATS-PFM-NOT-014-03 ATS-PFM-NOT-009-05 ATS-PFM-NOT-009-04
Preconditions
Jane has a delivered unread assignment notice.
Steps
End the assignment, read the old item and inspect the ending item and total.
Expected
The old wording remains readable outside unread results; the ending announcement is a separate unread item.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0004.spec.ts
04 A colleague cannot organize or investigate a personal item permissionnegative test
Exercises
CAP-PFM-NOT-009 CAP-PFM-NOT-010
Relies on
ATS-PFM-NOT-009-02 ATS-PFM-NOT-010-01
Preconditions
Jane and a colleague have personal access; the colleague lacks management authority.
Steps
The colleague lists, reads and marks Jane’s item and tries workspace History.
Expected
Jane’s item remains unchanged and neither personal detail nor administrator history exposes it to the colleague.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts
05 Responsibility screens and attention totals keep working regression test
Exercises
CAP-PFM-NOT-009 CAP-PFM-NOT-014
Relies on
ATS-PFM-NOT-009-09 ATS-PFM-NOT-014-01
Preconditions
Use the assignment dialog and capture attention totals before the change.
Steps
Save an explicit assignment through the console and compare responsibility, notice and attention views.
Expected
The responsibility persists and its notice appears; attention totals retain their own meaning.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/cross-application/NT-ACC-0300.spec.ts

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