Recruitment Requisition Events
Summary
Requisition submission, approval, rejection, and opening creation have audit/timeline effects but no dedicated domain or integration events.
Audience
Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.
Overview
Workflow-managed requisitions restrict direct decisions. Duplicate terminal callbacks acknowledge an already-decided requisition without reapplying it. Requisition, approval, rejection, and Job Opening creation have no exact domain-event types and therefore no domain-to-outbox mappings.
Workflow start/query/callback are HTTP boundaries, not event subscriptions. Audit and timeline entries are the only confirmed lifecycle evidence for these actions.
Requires confirmation
Consumer ownership, tenant-envelope policy, correlation/causation policy, retry limits, replay, ordering, contract governance, reconciliation, monitoring, and production support require confirmation.
Source References
microservices/src/recruitment-service/Application/Commands/RequisitionCommands.csmicroservices/src/recruitment-service/Domain/Recruitment/JobRequisition.csmicroservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.csmicroservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
Related Articles
See Also
Keywords
- Recruitment events
- Requisition Events
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly