Workflow Business Integrations
Summary
Leave, Expense, Asset, Performance and Recruitment services contain feature-gated typed clients that start and read Workflow instances. Their switches default off.
Business Purpose
Allow business modules to reuse Workflow approval decisions while retaining ownership of their records.
Actors
Workflow authors, approvers, delegates, process initiators, tenant administrators, product owners, support teams and owners of connected business modules.
Business Flow
| Module | Start/read client | Workflow subject | Terminal callback endpoint | Verified maturity |
|---|---|---|---|---|
| Leave | Implemented, feature-gated | Leave request | Implemented in Leave | Partial |
| Expense | Implemented, feature-gated | Expense claim | Implemented in Expense | Partial |
| Asset | Implemented, feature-gated | Asset request | Implemented in Asset | Partial |
| Performance | Implemented, feature-gated | Appraisal | Implemented in Performance | Partial |
| Recruitment | Implemented, feature-gated | Requisition | Implemented in Recruitment | Partial |
| Notification | No Workflow event mapping | Not applicable | None | Not implemented |
| Helpdesk, Payroll, Document, Employee/Organization | No Workflow client found | Not applicable | None | Not implemented |
Workflow Service publishes six lifecycle integration-event types through its hosted outbox relay.
Responsibilities
Authors maintain valid draft steps before publication. Initiating modules supply a subject and routing context. Approvers act only on applicable pending tasks. Tenant and service owners govern access, integration enablement and operational support.
Business Rules
Initiating services forward tenant/identity context and can fall back to a null client when disabled. Workflow starts only published keys.
Integrations
Workflow Service owns definitions, versions, instances and tasks. Connected modules can synchronously start and read instances when their integration is enabled; lifecycle domain events are persisted to an outbox and relayed as integration events.
Limitations
Workflow Service does not call the module callback endpoints, and no verified event consumer bridges terminal events to them. End-to-end source-record completion is therefore incomplete. Gateway Workflow routing was not found.
Requires Confirmation
Production enablement, approver-role naming, upstream access enforcement, terminal decision propagation, notification ownership, retention and operating procedures require confirmation.
Source References
microservices/src/leave-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/expense-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/asset-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/performance-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/workflow-service/Messaging/OutboxRelayHostedService.cs
Related Articles
See Also
Keywords
Workflow, approval, definition, version, task, delegation.
Revision Information
Draft source-backed business documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.