Recruitment Requisition Storage
Summary
Requisition persistence stores tenant lifecycle state, compatibility identity, decision evidence, Workflow reference, and created-opening reference.
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.
Overview
The requisition is an aggregate root with a primary key, a database-generated compatibility identity, string-converted status, bounded descriptive fields, and timestamps.
Three secondary indexes support compatibility identity, tenant/status queries, and Workflow-instance lookup; the compatibility identity is unique. Workflow and created-opening identifiers are logical references without configured foreign keys.
Approval can create a separate opening in the same Recruitment save boundary. External Workflow calls remain outside that transaction.
Requires confirmation
Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/recruitment-service/Domain/Recruitment/JobRequisition.csmicroservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs
Related Articles
See Also
Keywords
- Recruitment database
- Requisition Storage
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly