Event Overview

Summary

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

Audience

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

Reference Content

The scheduling write model and adjacent attendance event pipeline are separate. Scheduling commands persist canonical configuration and record audit/timeline evidence, but their aggregates do not raise events. Attendance records and punches raise lifecycle events that are translated during save.

Area	Verified behavior	Status
Shift and assignment changes	Synchronous persistence; audit/timeline entries	Not implemented for events
Policy and weekly-off changes	Synchronous persistence; audit/timeline entries	Not implemented for events
Leave holidays	Leave-owned synchronous calendar persistence	No scheduling event contract
Attendance lifecycle	Domain event to outbox to broker	Foundation/Partial
Cross-service orchestration	Three attendance event types accepted	Partial
Notifications	No attendance or scheduling event bindings	Not implemented

“Event” in an audit action or timeline entry means persisted history, not a broker-delivered integration event.

Source References

• microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/leave-service/Application/LeaveWorkflows.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