Leave Employee Profile Boundary

Summary

Leave maintains a local, event-driven projection of employee data needed for validation, identity bridging, display, and approver context.

Audience

Backend developers, architects, QA, Employee integrators, and support.

Overview

The projection contains identity bridges, tenant identity, display/contact categories, organization and manager context, joining date, status/activity, and last-applied event evidence. Employee Service remains the source owner.

The consumer handles created, updated, and employment-status events. It rejects missing tenant/legacy identity, detects duplicate event identity, ignores older events by occurrence time, upserts by tenant plus employee identity, derives active state from employment status, audits outcomes, and acknowledges only after persistence. Failures are requeued.

No deletion event is consumed, so deletion propagation is not confirmed. Reconciliation is required for missed events, identity-bridge changes, or prolonged staleness. Contact fields are present in the projection but should be minimized to actual Leave use.

Source References

• microservices/src/leave-service/Domain/Leave/EmployeeProfile.cs
• microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Employee Profile Boundary
• Technical architecture

Revision Information

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