Workflow API DTO Catalog
Audience
Developers, frontend engineers, QA, support, architects and implementation partners.
Summary
The application source declares 14 Workflow input/output records: seven request records and seven response records. Anonymous objects, persistence entities and shared service-information contracts are not counted as Workflow DTO declarations.
Reference Content
The tables below inventory every Workflow request and response record declared in the application DTO source.
Request records
| DTO | Purpose | Direction | Verified validation | Source path |
|---|---|---|---|---|
WorkflowConditionInput | Define one stage condition | Nested request | Blank field removed; operator/value otherwise permissive | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowStepInput | Define one authored step | Nested request | Approver type required/parsed; step type and mode default; limited structural checks | microservices/src/workflow-service/Application/Dtos.cs |
CreateWorkflowDefinitionInput | Create definition and initial steps | Request | Key/name required; tenant/key uniqueness; nested parsing | microservices/src/workflow-service/Application/Dtos.cs |
UpdateWorkflowDefinitionInput | Update definition and optional draft steps | Request | Optional fields; nested parsing when steps supplied | microservices/src/workflow-service/Application/Dtos.cs |
StartWorkflowInput | Start a published Workflow | Request | Definition identifier or key required; published version required | microservices/src/workflow-service/Application/Dtos.cs |
TaskDecisionInput | Carry optional decision comment | Request | Entire body optional for approval/rejection; no comment requirement | microservices/src/workflow-service/Application/Dtos.cs |
DelegateTaskInput | Carry destination and optional comment | Request | Destination must be nonblank | microservices/src/workflow-service/Application/Dtos.cs |
Response records
| DTO | Purpose | Direction | Construction | Source path |
|---|---|---|---|---|
WorkflowConditionDto | Condition projection | Nested response | Domain mapping | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowStepDto | Step projection | Nested response | Domain mapping | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowVersionDto | Version with ordered steps/conditions | Nested response | Domain mapping | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowDefinitionDto | Full definition graph | Response | Aggregate mapping | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowDefinitionSummaryDto | Definition list row | Response | Aggregate summary mapping | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowTaskDto | Task/worklist projection | Response/nested response | Entity mapping with optional Workflow key | microservices/src/workflow-service/Application/Dtos.cs |
WorkflowInstanceDto | Instance with ordered tasks | Response | Aggregate mapping | microservices/src/workflow-service/Application/Dtos.cs |
Non-DTO shapes
Health summary, message errors and outbox metadata use anonymous objects. Audit and timeline return persistence entities. Framework health and shared service information use framework/shared contracts.
Requires Confirmation
DTO evolution, nullability expectations, generated schema publication and separation of persistence diagnostic models require confirmation.
Source References
microservices/src/workflow-service/Application/Dtos.csmicroservices/src/workflow-service/Application/Mappings.csmicroservices/src/workflow-service/Application/Commands/WorkflowDefinitionCommands.csmicroservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
Related Articles
See Also
Keywords
Workflow API, approval endpoint, Workflow Service.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20