Attendance Reopen Events

Summary

Only approved reopen processing produces a dedicated lifecycle event. Request creation and request rejection are audited but do not publish dedicated contracts.

Audience

• Attendance developers, QA engineers, Payroll owners, and support engineers

Reopen flow

Approval first checks the external Payroll lock. If allowed, it resolves policy, recalculates the requested outcome, creates a missing daily record when necessary, applies the reopened result, approves the request, and saves AttendanceReopenedEvent.

When a missing daily record needs its generated identifier, the workflow performs an earlier save before the event-producing save. The reopen event and final Attendance/request changes share the latter transaction, not both saves.

No current service subscribes to AttendanceReopenedEvent. Reopen-requested and reopen-rejected contracts are Not implemented.

Source References

• microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
• microservices/src/attendance-service/Domain/Attendance/AttendanceReopenRequest.cs
• microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.cs
• microservices/src/contracts/Events/AttendanceLifecycleEvents.cs

Related Articles

• Attendance events
• Attendance technical documentation
• Attendance database documentation

See Also

• Attendance API documentation
• Attendance business documentation

Keywords

• Attendance events
• Integration contracts
• Eventual consistency

Revision Information

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