Audit and Timeline Storage

Summary

Attendance persists an audit log for technical/change accountability and a timeline for ordered Attendance configuration activity.

Audience

• Backend developers, QA engineers, support engineers, and auditors

Reference Content

Data flow

Both objects store tenant, entity type/identifier, actor context, occurrence time, and JSON metadata/details. Audit adds an action; timeline adds entry type, category, description, and metadata. Correlation identifiers are not modeled directly on either object and are Not implemented in these rows.

Both have tenant/time indexes and global tenant filters. Timeline queries are capped and newest-first; audit/timeline are explicitly written by application paths and are not universal EF change tracking. They should therefore be treated as operation-specific history, not proof that every database mutation was recorded. Structured details must remain public-safe when surfaced.

Source References

• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyQueries.cs

Related Articles

• Attendance database
• Attendance technical documentation
• Attendance API documentation

See Also

• Attendance business documentation
• Attendance overview

Keywords

• Attendance persistence
• EF Core
• PostgreSQL

Revision Information

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