Recruitment Workflow Integration
Summary
A feature-controlled synchronous HTTP integration delegates only requisition approval to Workflow Service and applies a terminal callback to Recruitment state.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
Direct decisions are blocked while the Submitted requisition is workflow-managed. Terminal callbacks are idempotent and can optionally be compared with live workflow state. Failure behavior is environment-sensitive and Transitional. There is no Workflow ownership for candidate, interview, offer, or onboarding actions.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/Application/WorkflowIntegration.csmicroservices/src/recruitment-service/Application/Commands/RequisitionCommands.csmicroservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/recruitment-service/Domain/Recruitment/JobRequisition.cs
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Workflow Integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly