Skip to main content

Notification Source Map

Summary

This reference maps notification business claims to the extracted service, main application controllers and client portal source that supports them.

Audience

Product owners, engineers, QA, support teams, architects, security reviewers and documentation maintainers.

Business Purpose

Make every major statement in this business documentation reviewable against backend and frontend source without exposing environment configuration or operational secrets.

Actors

Product owners, engineers, QA, support teams, architects, security reviewers and documentation maintainers.

Business Flow

Reviewers start with the claimed capability, inspect its primary source, compare the connected UI where applicable, and record business meaning or uncertainty in the corresponding article.

Responsibilities

Documentation owners refresh this map when code boundaries change. Engineering confirms technical interpretation. Product validates business terminology and status. Security reviews public exposure.

Business Rules

Repository source is evidence of implementation, not proof of runtime enablement. Public documentation omits provider credentials, infrastructure addresses, messaging topology and environment-specific values.

Reference Content

Business areaPrimary source evidenceDocumented in
Entities, statuses and audit stagesmicroservices/src/notification-service/Domain/NotificationEntities.csOverview, lifecycle, history, compliance
Dispatch orchestration and outcomesmicroservices/src/notification-service/Application/NotificationDispatcher.csLifecycle, delivery, retry, rules
Event coverage and audiencesmicroservices/src/notification-service/Application/EventNotificationResolver.csIntegrations, limitations
Preferencesmicroservices/src/notification-service/Application/PreferenceEvaluator.csDelivery, rules, limitations
Rendering and template precedencemicroservices/src/notification-service/Application/TemplateEngine.csTemplate management, rules
Default template inventorymicroservices/src/notification-service/Seed/DefaultTemplateSeeder.csTemplate management, integrations
Automatic retrymicroservices/src/notification-service/Application/RetryPolicy.csRetry handling, rules
Senders and channel readinessmicroservices/src/notification-service/Channels/Channels, delivery, limitations
Consumer and envelopemicroservices/src/notification-service/Messaging/Lifecycle, integrations
Persistence and tenant query modelmicroservices/src/notification-service/Infrastructure/NotificationDbContext.csRules, compliance
Service operations and statisticsmicroservices/src/notification-service/Api/NotificationEndpoints.csAdmin, dashboards, history
Service registration/security evidencemicroservices/src/notification-service/Program.csAdmin, compliance, limitations
Authenticated legacy inboxControllers/NotificationsController.csEmployee experience, history, rules
Legacy template model/accessControllers/NotificationTemplatesController.csTemplate management, admin, rules
Employee inbox UIUI/salary-ui/apps/client-hrms-portal/src/pages/NotificationsPage.tsxEmployee experience
Template editor UIUI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationTemplateManagementPage.tsxTemplate management, admin
Operations center/dashboard UIUI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationCenterAdminPage.tsx; OperationsAdminPages.tsxAdmin, dashboards

Integrations

The map spans the extracted notification service, main application controllers and client HRMS portal because current business behavior crosses all three boundaries.

Limitations

No deployment manifests, live environments, provider consoles, database contents or operational logs were treated as authoritative evidence. Exact runtime enablement remains unknown.

Requires Confirmation

Confirm repository ownership, canonical implementation, production feature flags, provider choices, access gateway controls and the source list for the next review.

Source References

  • microservices/src/notification-service/
  • Controllers/NotificationsController.cs
  • Controllers/NotificationTemplatesController.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/NotificationsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationCenterAdminPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationTemplateManagementPage.tsx

See Also

Keywords

Source map, traceability, evidence, backend, frontend.

Revision Information

Draft; reviewed 2026-07-21; next quarterly review 2026-10-21.