Leave Event Integration

Summary

This page records the verified Workforce Scheduling event boundary and its adjacent Attendance integration behavior.

Audience

Developers, integration engineers, leave engineers, QA engineers, and solution architects.

Reference Content

Leave Service owns leave-request events and calendar persistence, but no verified event connects leave holidays or weekly-off changes to Workforce Scheduling. Scheduling does not consume the six Leave domain events or their integration contracts.

Boundary	Verified behavior
Approved/rejected leave	Leave lifecycle events exist in Leave Service
Holiday calendar	Read and written through Leave workflows
Weekly-off calendar	Leave-owned storage remains separate
Scheduling synchronization	No publisher, consumer, or contract found

Cross-context calendar alignment is therefore Transitional and event-driven propagation is Not implemented.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveDomainEvents.cs
• microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs

Related Articles

• Events overview
• Event limitations
• Event source map

See Also

• Technical documentation
• API documentation
• Database documentation

Keywords

• Workforce Scheduling events
• Attendance integration contracts
• Transactional outbox

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20