Notification Event Integration

Summary

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

Audience

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

Reference Content

The Notification Service has a broker consumer and an explicit supported-event resolver. That list includes Leave and Payroll events but none of the five Attendance lifecycle events and no scheduling-change type.

Consequently:

• shift, assignment, policy, weekly-off, and holiday changes do not generate verified notifications;
• attendance submit, approve, reject, punch, and reopen messages are not bound by this notification resolver;
• no scheduling notification template or recipient mapping was found;
• delivery channel behavior for future scheduling notifications requires confirmation.

Source References

• microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/contracts/Events/AttendanceLifecycleEvents.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