Skip to main content

Value Conversions

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​

Canonical weekday enum values use an explicit string conversion with a bounded length. Policy and shift hour values and rule thresholds use fixed numeric precision. Audit/timeline metadata uses a provider JSON type.

Temporal values​

Shift boundaries are TimeOnly values and have no explicit custom converter in the context. Assignment dates and timestamps use their CLR temporal types. Date normalization occurs in domain/application code before persistence.

Compatibility conversion​

Legacy shift times are stored as text. A compatibility mapper parses accepted time text into canonical time values. Legacy overtime wording is reduced to a numeric hour threshold and rendered back to text. Values outside the supported numeric interpretation fall back according to compatibility service behavior.

Non-persisted conversions​

Scheduled shift duration is derived in memory. Effective-policy provenance and probe results are projections, not stored columns.

Source References​

  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
  • microservices/src/attendance-service/Application/TimeOffice/ShiftPolicyMappings.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatContracts.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