Workflow and Notification Integration
Summary
The verified extracted Workflow integration applies to requisition approval, not onboarding or offboarding orchestration. Notification coverage is similarly partial: monolith exit approval has a notification event, while the extracted notification resolver does not map the inspected Recruitment onboarding events.
Audience
Developers, QA, support engineers, notification owners, and solution architects.
Workflow behavior
The Workflow client is registered behind feature selection and has a null/local fallback path. This does not establish an onboarding approval, checklist workflow, or offboarding clearance workflow.
Notification behavior
The presence of a domain event or outbox record does not prove user notification. A consumer/resolver and configured delivery channel are also required.
Failure behavior
Workflow client failures are logged by the integration boundary and need operational handling. Notification delivery state, retry policy, and channel configuration were not established by the onboarding/offboarding source inspection. Lifecycle commands do not form a transaction with message delivery.
Requires confirmation
- Whether onboarding and exit approval should be modeled in Workflow Service.
- Required recipients, templates, channels, localization, retry, and escalation rules.
- Ownership for mapping Recruitment lifecycle events in Notification Service.
- Whether failed notifications should affect lifecycle state.
Source References
microservices/src/recruitment-service/Application/WorkflowIntegration.csmicroservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/notification-service/Application/EventNotificationResolver.csControllers/NotificationTemplatesController.csmicroservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
Related Articles
See Also
Keywords
- Workflow integration
- Notification resolver
- Exit approval
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly