Skip to main content

Workflow Business Source Map

Summary​

This map identifies the authoritative source for Workflow business capabilities and verified adjacent integrations.

Business Purpose​

Give reviewers a reproducible route from documented claims to implementation evidence.

Actors​

Workflow authors, approvers, delegates, process initiators, tenant administrators, product owners, support teams and owners of connected business modules.

Business Flow​

ConcernSource path
Definition/version modelmicroservices/src/workflow-service/Domain/Workflow/WorkflowDefinition.cs
Instance/task/action modelmicroservices/src/workflow-service/Domain/Workflow/WorkflowInstance.cs
States and approver typesmicroservices/src/workflow-service/Domain/Common/Enums.cs
Definition commandsmicroservices/src/workflow-service/Application/Commands/WorkflowDefinitionCommands.cs
Approval enginemicroservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
Worklist/reporting queriesmicroservices/src/workflow-service/Application/Queries/WorkflowQueries.cs
Public inputs/outputsmicroservices/src/workflow-service/Application/Dtos.cs
Endpoints/access foundationmicroservices/src/workflow-service/Api/WorkflowEndpoints.cs and Policies.cs
Tenant/audit/outbox persistencemicroservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs and Persistence.cs
Development workflowsmicroservices/src/workflow-service/Infrastructure/DevelopmentSeeder.cs
Lifecycle events/relaymicroservices/src/workflow-service/Messaging/WorkflowIntegrationEvents.cs and OutboxRelayHostedService.cs
PortalUI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
NavigationUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
Adjacent clientsLeave, Expense, Asset, Performance and Recruitment WorkflowServiceClient.cs files

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​

Only static source was inspected. Repository-relative source references are the review boundary.

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​

No runtime configuration, database content, effective route deployment or consumer topology was verified.

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/workflow-service/Domain/Workflow/WorkflowDefinition.cs
  • microservices/src/workflow-service/Domain/Workflow/WorkflowInstance.cs
  • microservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
  • microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx

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.