Leave Notification Integration

Summary

Notification Service resolves confirmed approved and rejected Leave events; monolith approval also has a direct notification path.

Audience

Leave/Notification developers, architects, QA, support, and product engineers.

Overview

The extracted Notification resolver supports LeaveApproved and LeaveRejected, resolves an employee recipient reference, and produces in-app/email intents from service-owned templates. LeaveRequested, LeaveCancelled, balance updates, and encashment are not confirmed notification intents.

The broker/consumer boundary is eventually consistent. Notification Service owns templates, channels, delivery, retries, and recipient resolution. Leave owns event publication only. Monolith approval can dispatch directly, creating Transitional parity differences. Delivery success and retry behavior belong to the later Events/Operations documentation.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveDomainEvents.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/notification-service/Seed/DefaultTemplateSeeder.cs
• Controllers/LeaveRequestsController.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Notification Integration
• Technical architecture

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly