Workflow Development Seeding
Summary
One static seeder runs only during eligible Development startup after migration handling.
Seed content
The implementation ensures five published sequential approval definitions representing leave, expense, recruitment requisition, asset and appraisal flows. The source comment says three, but the executable body contains five.
Idempotency
Each definition is checked by fixed development tenant plus key while ignoring query filters. Existing keys are skipped. Missing definitions are created, given steps, published and saved individually.
Isolation
The seeder uses a design/startup context capable of bypassing tenant filters. It is not registered for non-Development startup.
Limitations
No seed version reconciliation, update of existing definitions, rollback or dedicated seeder test exists.
Requires Confirmation
Development data ownership, reset strategy and handling when seed definitions evolve require confirmation.
Source References
microservices/src/workflow-service/Infrastructure/DevelopmentSeeder.csmicroservices/src/workflow-service/Program.csmicroservices/src/workflow-service/Domain/Workflow/WorkflowDefinition.cs
Related Articles
See Also
Keywords
Workflow database, EF Core, Workflow schema.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20