Skip to main content

Workflow Queries

Summary

The read side combines WorkflowQueries with a small definition loader and one direct health-data query in endpoint code.

Query catalog

  • Definitions are listed by key as summaries.
  • One full definition is loaded with versions, steps and conditions.
  • One instance is loaded by identifier with tasks.
  • The caller worklist returns matching Pending user/role tasks.
  • Audit, timeline and outbox feeds are ordered newest-first and bounded to a maximum page size.
  • Health data counts definitions, published definitions, instances and pending tasks.

Data access

Queries use EF Core no-tracking reads. Tenant global filters apply automatically. The worklist joins tasks to instances to add the workflow key.

Output boundaries

Outbox reads expose selected operational fields instead of stored payload JSON. Full definition and instance mapping use application DTOs.

Limitations

No pagination cursor, instance listing, completed worklist, task search, definition filtering, metrics aggregation or dedicated report query exists.

Requires Confirmation

Reporting ownership, pagination standards and super-administrator read expectations require confirmation.

Source References

  • microservices/src/workflow-service/Application/Queries/WorkflowQueries.cs
  • microservices/src/workflow-service/Api/WorkflowEndpoints.cs
  • microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs

See Also

Keywords

Workflow architecture, approval engine, Workflow Service, technical foundation.

Revision Information

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