Skip to main content

Attendance Employee Profile Boundary

Summary​

EmployeeProfile is Attendance's local supporting projection and is not the employee master record.

Audience​

Backend developers, Employee/Attendance integrators, architects, and QA engineers.

Purpose and data categories​

The projection supplies employee activity, joining date, display/organization context, reporting-manager context, attendance mode, standard-hours and status-threshold fallbacks, and a legacy shift snapshot. Attendance uses it to validate active/joining-date behavior, label query results, build a roster, and fill gaps when no effective shift or default policy value applies.

A service capability supports explicit profile upsert, confirming direct/API-driven population. No Attendance event consumer that automatically synchronizes Employee lifecycle events is present. Missing profiles do not universally block attendance; some paths continue with default calculation context. This makes the boundary Transitional.

Employee Service remains responsible for master data. Attendance should minimize copied fields, define freshness and deletion handling, and avoid treating its projection as authoritative outside attendance use cases. Event synchronization, reconciliation, versioning, stale-profile detection, and ownership of manual correction are Requires confirmation.

Source References​

  • microservices/src/attendance-service/Domain/Attendance/EmployeeProfile.cs
  • microservices/src/attendance-service/Domain/Attendance/EmployeeAttendancePolicy.cs
  • microservices/src/attendance-service/Application/Services/EmployeeProfileService.cs
  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Application/Dtos.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Employee Profile Boundary

Revision Information​

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