Skip to content

JNY-PFM-NOT-003Investigate recipient and empty-request history

Markdown

JNY-PFM-NOT-003

Investigate recipient and empty-request history

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

KindJourneyProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision1End-to-endRequired

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Goal
Determine which staff received a notice, inspect its delivery explanation and identify requests that produced no items.
Screens
/console/{tenantId}/settings/notifications
Intent sources
services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#2. Scope

Steps

#SurfaceActionCapabilityExpectedProvenance
1/console/{tenantId}/settings/notificationsThe administrator visits notification History in Settings.CAP-PFM-NOT-011Rows list recipients, notification types, times and states in descending time order.test
2listNotificationHistoryThe administrator filters the recipient picker to Jane.CAP-PFM-NOT-011History retains Jane's rows only.test
3getNotificationRequestThe administrator opens an item's diagnostic chain.CAP-PFM-NOT-011Detail links the request, recipient explanation and deliveries; intended unused e-mail wording includes its future milestone.test
4listNotificationRequestsThe administrator selects Requests.CAP-PFM-NOT-003An outsider-audience request shows isolation refusal, and a two-hundred-and-one-person audience shows invalidity.test

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate4The administrator selects an outcome filter in Requests.The list returns only that outcome in descending time order.Invalid requests can be located through their outcome filter.test
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#narrows by outcome, definition and since, newest first, and pages by keyset
failure1A staff caller lacking notification-management permission attempts History.History and its diagnostic operations deny access.No workspace history content is returned.test
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#refuses History and the chain to a caller with only platform.notifications.use
failure3The delivery table presents an unused channel.Its current wording omits the future milestone despite displaying the reason.The pinned handoff retains this known defect.documented

Assertions

IdStatementProvenance
01History identifies Jane and the item's type, time and state without exposing another workspace's activity.test
02Diagnostic detail explains each unused channel.test
03Requests producing no notices retain their outcome and explanation in the list.test

End-to-end policy: required: Recipient filtering, request selection and diagnostic navigation are console behavior, and browser acceptance exposes the outstanding delivery-explanation defect.

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.