Render recipient-specific notification content

Purpose

Recipients receive understandable content and a destination appropriate to their workspace and language.

How It Works

Platform loads the registered wording for each recipient. Locale fallback chooses a usable template, and time formatting uses the recipient's time zone. Request data is combined with trusted rendering objects. Destination construction uses the notice workspace rather than a producer-selected console origin. Oversized console content is truncated at rendering limits. Declared links are redacted from retained request values after use. The console opens the rendered destination according to its internal or external form. Resource names require console presentation because Platform does not own those names.

The rule rows define this outcome; the acceptance set identifies existing proof and proposed checks. Implementation evidence alone does not approve the observed details.

Relationships

Registration supplies the event contract that later work validates and renders.

Recipient selection supplies the eligible people and their audience explanations.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

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

Outcomes: Each eligible recipient receives content rendered for that person.Navigation uses an absolute destination when the console base is configured; retained request data conceals declared link values.
Surfaces: jobconsole
Intent sources: services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#PLAT-M23-S01

Controls

21 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-PI-001 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Business Rules

8 rules, 4 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Rendering uses each recipient's locale and time zone; an unavailable regional locale falls back to its language, and an undeclared language falls back to English. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/unit/render-message.spec.js#renders an instant in the recipient’s zone, not the server’s
`02` Proposed	Template inputs combine request data with Platform-supplied recipient, organization, subject-record and destination objects.	policy	service	test services-platform:modules/notifications/tests/unit/render-message.spec.js#renders the platform’s four objects: the person, the organization, the record and the destination
`03`must prove Proposed	Console rendering truncates titles beyond 140 characters and bodies beyond 2,000 instead of rejecting delivery. no proof recorded yet	calculation	service	test services-platform:modules/notifications/tests/unit/render-message.spec.js#cuts a title longer than 140 characters rather than refusing the notification
`04`must prove Proposed	Console destinations are workspace-relative and open in the notice's workspace; other channels use its console base address when available; HQ destinations retain their HQ path, and missing route parameters prevent destination construction. no proof recorded yet	calculation	service, console	test services-platform:modules/notifications/tests/unit/render-message.spec.js#gives the in-app record the tenant-relative path, and every other channel the absolute link under the workspace
`05`must prove Proposed	After rendering, retained data replaces declared link values with a redaction marker while preserving their fields. no proof recorded yet	policy	service	test services-platform:modules/notifications/tests/integration/services/orchestration/orchestrate-request.integration.spec.js#redacts a url field of the data from the request after it was rendered
`06` Proposed	The resulting notice includes category, severity, subject-record identity and label, and occurrence time.	policy	service	test services-platform:modules/notifications/tests/unit/render-message.spec.js#carries the severity, the record and the instant it happened
`07` Proposed	The console opens internal workspace routes in the current tab and absolute HTTPS destinations in another tab.	policy	console	test react-console:components/notifications/__tests__/destination.test.ts#keeps an absolute https link and opens it in a new tab
`08` Proposed	Platform does not resolve resource names for responsibility wording; Organization-wide notices name the organization; scoped notices leave resource naming to the console.	policy	service, console	documented services-platform:docs/notifications.md#9. Producers

Scenarios

Id	Given	When	Then	Provenance
`01`	Jane's Northeast assignment uses English locale and Eastern time.	Platform renders her assignment item.	Recipient content and time formatting follow her settings, and its action reaches My Responsibilities in her workspace.	inferred services-platform:modules/notifications/services/orchestration/render-message.ts:renderNeutralMessage

Planning

Render recipient-specific notification content ​

Purpose ​

How It Works ​

Relationships ​