Workflow Delegation
Summary
Delegation reassigns a pending task from its current user/role target to a named user.
Business Purpose
Allow decision work to move to another individual without resolving the task.
Actors
Workflow authors, approvers, delegates, process initiators, tenant administrators, product owners, support teams and owners of connected business modules.
Business Flow
The delegate action requires a destination user, writes that value to AssignedTo, clears AssignedRole, stores DelegatedTo and records action/audit/timeline evidence. The task remains Pending.
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 a Pending task in a Running instance may be delegated. Blank destination is rejected.
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
There is no delegate authorization check, delegation chain, return-to-owner, expiry, proxy period, role delegation or Delegated task status transition.
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/WorkflowInstance.csmicroservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.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.