Skip to main content

Entity Relationships

Audience​

Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling persistence behavior and boundaries.

Summary​

Only two explicit database relationships were verified in the scheduling scope. Other associations are scalar identifiers resolved by application queries.

Explicit relationships​

Policy owns many rules through a foreign key with cascade deletion. In the monolith, a legacy employee has an optional shift relationship; deleting the shift clears that reference.

Scalar-only associations​

Canonical assignment stores shift and employee references without mapped navigation or foreign key. Audit and timeline store entity type/reference text without foreign keys. Holidays and weekly offs are independent calendar rows.

Consequence​

Application code must preserve referential and tenant consistency for scalar-only links. Database cascades apply only to the verified explicit relationships.

Source References​

  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
  • microservices/src/attendance-service/Domain/TimeOffice/AttendancePolicy.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Workforce Scheduling database
  • Shift persistence
  • Attendance policy storage

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20