Skip to main content

Development Seeding

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​

Attendance and Leave both contain development-only seed behavior. No seeder was run during this documentation work.

Attendance seed​

The Attendance seeder creates one example shift, one weekly-off rule, and one default attendance policy with an ordered status-rule ladder for a fixed development tenant. Each component checks for existing data independently and bypasses tenant filters because no request tenant exists.

The default policy is only marked default if the tenant does not already have one. Each component is saved separately. No employee assignment is seeded.

Leave seed​

The Leave seeder creates development calendar and leave configuration, including a weekly-off row and example holidays, when a fixed development tenant lacks them. It also bypasses query filters. Seed failures are logged and do not prevent startup in the reviewed flow.

Classification​

Development seeding is Implemented and environment-gated. Production seed policy, sample-data cleanup, and fixed-tenant governance require confirmation.

Source References​

  • microservices/src/attendance-service/Infrastructure/DevelopmentSeeder.cs
  • microservices/src/attendance-service/Program.cs
  • microservices/src/leave-service/Infrastructure/DevelopmentSeeder.cs
  • microservices/src/leave-service/Program.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