Notification Integrations
Business Purpose
Define which business domains can currently request notification processing and what information they must supply.
Actors
Originating-module owners, notification owners, provider administrators, architects, QA and support teams.
Business Flow
The extracted resolver maps 42 event types: Employee (1), Leave (2), Payroll (2), Document (1), tenant provisioning (1), Expense (3), Asset (6), Performance (7), Training (9) and Helpdesk (10). Most default to in-app and email; payroll freeze defaults to in-app only. Some events map to audience-specific or differently named template keys.
Responsibilities
Publishers provide stable identifiers, tenant, occurrence time, correlation data and payload fields needed for recipient and template variables. Notification owners keep mappings and seeded templates synchronized. Provider owners maintain channel readiness without exposing operational configuration in public documentation.
Business Rules
Only registered event types are consumed. Channel overrides may alter requested channels but do not bypass preferences, recipient addresses, templates or sender availability. Email intent is actionable only when an email address resolves.
Integrations
| Boundary | Current evidence | Business implication |
|---|---|---|
| HR domain events | 42 explicit resolver mappings | Event support is allow-listed, not generic |
| Recipient directory | Upserted from event-derived identities | Events can refresh recipient contact data |
| Channel senders | In-app plus configurable email and placeholder mobile channels | Provider readiness varies by channel |
| Portal | Employee inbox, legacy template editor, admin operations and dashboards | UI spans both implementation paths |
Limitations
Workflow lifecycle events are not in the extracted resolver. Recruitment-specific event coverage is absent there, although the legacy catalog includes recruitment and interview templates. Queue topology and deployment wiring were intentionally excluded from this public business documentation.
Requires Confirmation
Confirm producer enablement, event schema governance, delivery ownership for Workflow and Recruitment, compatibility monitoring, tenant guarantees and unsupported-event handling.
Source References
microservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/notification-service/Messaging/NotificationEventConsumer.csmicroservices/src/notification-service/Messaging/NotificationEventEnvelope.csmicroservices/src/notification-service/Seed/DefaultTemplateSeeder.cs
Related Articles
See Also
Keywords
Integration, business event, producer, recipient, provider.
Revision Information
Draft; reviewed 2026-07-21; next quarterly review 2026-10-21.