Skip to main content

Workflow API Validation

Summary​

Validation is distributed across route constraints, command checks, aggregate invariants, state guards and persistence constraints. No validation middleware or dedicated Workflow validator exists.

Validation pipeline​

Route validation​

Identifier paths use GUID constraints. Diagnostic take inputs are optional integers and are clamped by queries.

Request validation​

Definition creation requires key/name and recognized approver types. Start requires a definition selector. Delegation requires a destination. Approval/rejection bodies are optional.

Domain and state validation​

Publication requires a nonempty draft. Published versions reject editing. Task actions require Running/Pending state.

Missing validation​

Step order, condition operators, approver-value completeness, comment lengths before persistence, task assignment and concurrency are not comprehensively checked.

Requires Confirmation​

Standard validation details, stricter authoring rules and assignment-aware validation require confirmation.

Source References​

  • microservices/src/workflow-service/Api/WorkflowEndpoints.cs
  • microservices/src/workflow-service/Application/Commands/WorkflowDefinitionCommands.cs
  • microservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
  • microservices/src/workflow-service/Domain/Workflow/WorkflowDefinition.cs
  • microservices/src/workflow-service/Api/EndpointResults.cs

See Also​

Keywords​

Workflow API, approval endpoint, Workflow Service.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20