Skip to main content

Template Management

Business Purpose​

Allow controlled message customization without changing each originating HR module.

Actors​

Tenant administrators, super administrators, product/content owners, implementation partners, recipients and support teams.

Business Flow​

The extracted service seeds 87 global rows across 44 keys: 44 in-app and 43 email templates. It selects the highest active tenant version, then falls back to the highest active global version. The legacy editor exposes eight defined events and stores in-app and email content together.

Responsibilities​

Content owners maintain accurate, accessible wording and approved variables. Tenant administrators test overrides. Platform owners prevent confusion between the versioned service model and the legacy event-key model.

Business Rules​

Extracted-service creation increments the key/channel version; updates can edit an existing row. Missing render variables become empty text. The legacy editor requires authorized super-admin or tenant-admin access, previews sample data and resets to a default or inherited record according to scope.

Integrations​

Templates depend on resolver keys and event payload variables. The dedicated portal editor matches the legacy controller contract, not the extracted service's identifier/version contract.

Limitations​

Locale is stored by the extracted service but is not used for selection. No approval workflow, scheduled publishing, content revision comparison or unified editor was found. The two catalogs cover different events.

Requires Confirmation​

Confirm the canonical catalog, content approval roles, permitted HTML, branding, localization roadmap, tenant inheritance semantics and migration strategy.

Source References​

  • microservices/src/notification-service/Application/TemplateEngine.cs
  • microservices/src/notification-service/Seed/DefaultTemplateSeeder.cs
  • microservices/src/notification-service/Api/NotificationEndpoints.cs
  • Controllers/NotificationTemplatesController.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationTemplateManagementPage.tsx

See Also​

Keywords​

Template, default, tenant override, preview, version, render.

Revision Information​

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