Rhythm 2.0 Specifications

Appearance

ATS-PFM-NOT-014Announce explicit responsibility changes: Capability Test Specification

Markdown

ATS-PFM-NOT-014

Announce explicit responsibility changes: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-NOT-014

Design

Executed by
TST-PFM-NOT-005, TST-PFM-NOT-008

KindAcceptance test setProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision2

Read atservices-platform ad3f6a65react-console baf6dae3

Announce explicit responsibility changes: Capability Test Specification ​

Coverage ​

Each scenario names the guarantee it proves. Category coverage describes specified cases; executable bindings retain their narrower assertion boundaries. Lifecycle coverage remains a gap wherever guards and effects lack independent verification.

RuleProof
BR-CAP-PFM-NOT-014-01ATS-PFM-NOT-014-01, ATS-PFM-NOT-014-07
BR-CAP-PFM-NOT-014-02ATS-PFM-NOT-014-02
BR-CAP-PFM-NOT-014-03ATS-PFM-NOT-014-03
BR-CAP-PFM-NOT-014-04ATS-PFM-NOT-014-04
BR-CAP-PFM-NOT-014-05ATS-PFM-NOT-014-05
BR-CAP-PFM-NOT-014-08ATS-PFM-NOT-014-06
BR-CAP-PFM-NOT-014-09FND-PFM-NOT-075

Prepare Jane and Sam, two scopes and a delegation spanning several responsibilities. Assign responsibilities, process notices, read each recipient inbox, fold same-scope repeats and end one assignment.

The interaction case combines the producing, processing and reading outcomes named in its frontmatter. It remains proposed until an executable suite performs that complete sequence.

Coverage

  • Rule covered
  • Transition covered
  • Validation gap: FND-PFM-NOT-075
  • Permission covered
  • Edge gap: FND-PFM-NOT-075
  • Failure covered
  • Boundary gap: FND-PFM-NOT-075
  • Concurrency gap: FND-PFM-NOT-075
  • Invariant covered
  • Interaction covered

Test Scenarios

7 scenarios proving CAP-PFM-NOT-014; 2 bound to an existing test.

01 Announce an explicit responsibility assignmentruleapitest
Proves
BR-CAP-PFM-NOT-014-01
Preconditions
Use a clerk account for Jane and a Northeast Batch posting responsibility.
Steps
Save an administrator-created assignment to Jane.
Expected
Within the acceptance polling interval Jane receives one unread item with content, subject record and a destination to My Responsibilities.
Data
Use only records created and owned by this suite.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0001.spec.ts#NT-ACC-0001
02 Notify both sides of a delegationinteractionapiproposed
Proves
BR-CAP-PFM-NOT-014-02
Preconditions
Jane has Batch posting; Sam is a colleague.
Steps
Delegate Jane's responsibilities to Sam for seven days.
Expected
Sam receives one delegation item, Jane receives confirmation and other users receive no notice.
Data
Use only records created and owned by this suite.
Source
services-platform:docs/notifications.md#9. Producers
03 Withdraw assignment wording and announce its endtransitionapitest
Proves
BR-CAP-PFM-NOT-014-03
Preconditions
Jane's delivered assignment announcement is still unread.
Steps
Remove Jane's assignment using the administrator session.
Expected
The old item becomes inapplicable and leaves unread totals; the assignee receives an ending item.
Data
Use only records created and owned by this suite.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0004.spec.ts#NT-ACC-0004
04 Exclude the acting administratorpermissionapiproposed
Proves
BR-CAP-PFM-NOT-014-04
Preconditions
Prepare a administrator who also has the use permission.
Steps
They assign and next end Jane's responsibility.
Expected
Jane receives the assignment and ending items while the administrator's inbox remains unchanged.
Data
Use only records created and owned by this suite.
Source
services-platform:docs/notifications.md#9. Producers
05 Publish nothing for a rolled-back assignmentinvariantapiproposed
Proves
BR-CAP-PFM-NOT-014-05
Preconditions
Prepare a assignment that will fail to save.
Steps
Try the assignment operation.
Expected
No notification request commits and no recipient receives an item.
Data
Use only records created and owned by this suite.
Source
services-platform:docs/notifications.md#9. Producers
06 Preserve assignment on publication refusalfailureapiproposed
Proves
BR-CAP-PFM-NOT-014-08
Preconditions
Prepare a recipient whose display name looks like an e-mail address.
Steps
Save the responsibility assignment for those users.
Expected
The assignment persists; the rejected notice is logged and no notification is sent.
Data
Use only records created and owned by this suite.
Source
services-platform:docs/notifications.md#9. Producers
07 Responsibility announcements stay distinct across folding and withdrawalinteractionapiproposed
Proves
BR-CAP-PFM-NOT-014-03
Preconditions
Prepare Jane and Sam, two scopes and a delegation spanning several responsibilities.
Steps
Assign responsibilities, process notices, read each recipient inbox, fold same-scope repeats and end one assignment.
Expected
Recipients see their own assignment and delegation outcomes. Ending one scope leaves the other scope intact, and withdrawal removes the ended assignment from applicable unread results.
Data
A suite-owned workspace, named staff accounts and unique occurrence keys; external adapters record attempts without shared writes.
Source
rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-014-tell-staff-about-changes-to-their-own-responsibilities.md#frontmatter,rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-009-work-through-my-own-notifications.md#frontmatter,rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#frontmatter

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