Workflow Approvals
Summary
Approval changes one pending task to Approved and may advance or complete the instance.
Business Purpose
Collect the required decisions for each applicable stage in order.
Actors
Workflow authors, approvers, delegates, process initiators, tenant administrators, product owners, support teams and owners of connected business modules.
Business Flow
Multiple steps with the same order are opened together and all must be decided before approval advancement.
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
Approval is allowed only while the instance is Running and the task Pending. Approved tasks record actor, comment and decision time.
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
StepMode is not consulted by the engine; same-order behavior is effectively all-open/all-required. The actor is not checked against AssignedTo or AssignedRole.
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/Application/Commands/WorkflowInstanceCommands.csmicroservices/src/workflow-service/Domain/Workflow/WorkflowInstance.csmicroservices/src/workflow-service/Domain/Common/Enums.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.