Notification Submission
What It Is
This record is superseded. The notification submission is a facet of Staff Notification, and the permanent record remains available for historical references. The active staff model combines declarations, transactional requests, recipient items and delivery history.
A notification submission records that an application wants Platform to announce an event. The producer describes the audience instead of assembling channel addresses. Platform can then evaluate current staff membership and responsibility holders when work is processed. The submission remains useful as a history record even when it reaches nobody.
This distinction matters when a business transaction is retried or an event is withdrawn. The submission identity links retries to the same work, while its result distinguishes acceptance from invalid data, an empty audience or expiry. A receipt is acknowledgement of publication; it does not establish that a recipient has received or read anything.
What It Is Not
A submission is neither an inbox item nor proof of delivery. Its audience can resolve to no eligible users. It is also separate from association e-mail submission, even though both systems use transactional queue publication. The two models select recipients and render content for different purposes.
How It Is Used
The producer writes publication work alongside its business change using a restricted capability role. After commit, dispatch and consumer processing validate the definition, resolve recipients and create notices. Future-dated work waits, and expired work stops. Producers cancel or replace events that no longer apply. Reconciliation closes requests after expiry and completion of pending delivery work.
Its Facets
Event identity. A producer-selected event key derives the request identifier and recognizes repeated submissions. Make transaction retries refer to the existing request.
Recipient selection. Entries specify users, scoped responsibilities, roles or permissions, with optional reasons, exclusions and actor inclusion. Resolve current staff recipients during processing.
Event context. Declared data, a subject record and optional responsibility scope accompany the announcement. Support rendering, navigation and collapse matching.
Delivery interval. Optional not-before and expiry instants bound when the request remains useful. Delay future work and reject stale delivery.
Replacement and withdrawal. A replacement key links successor events; cancellation withdraws an earlier request. Keep notices aligned with the underlying event.
Processing result. Acceptance, empty audiences, invalidity, replacement, expiry and cancellation explain how processing ended. Include unsuccessful and recipient-less submissions in history.
Rejected outsiders. Processing records named users removed by the customer and account boundary. Explain isolation decisions rather than silently losing recipients.
Closure. Settlement follows expiry and completion of outstanding work, closing further request changes. Retain cancellation opportunities while the request remains open.
Transactional queue entry. The producer inserts short-lived publication work in its business transaction. Tie dispatch availability to business commit.
HQ selection. Only the reserved system workspace can address the system audience. Select Slack channels for operational alerts without selecting customer staff.
How It Relates
The registered notification type bounds the submission's audience and data. One accepted submission may create several recipient notices; collapse can make several submissions contribute to one notice. The request remains the audit connection between producer activity and what recipients encountered.
What It Could Become
The product should resolve whether an ending event remains useful when its original assignment announcement never reached the recipient. Producer adoption also needs the shared submission role confirmed by the owning infrastructure work. Future planning should preserve inspectable empty and invalid outcomes rather than treating publication receipts as delivery success.