Workflow Events & Integration Contracts
Audience
Developers, QA, support, operations, architects, security reviewers and implementation partners.
Overview
This documentation set covers Workflow event creation, contracts, outbox publication, downstream integration boundaries and verified limitations.
Summary
Workflow implements six domain events and six one-to-one integration-event contracts. Aggregate events are mapped into the transactional outbox during save, and a Workflow-owned hosted relay uses shared messaging infrastructure to publish pending or failed records.
The runtime is Transitional. Publishing is wired, but no verified Workflow-event consumer, Notification mapping, Gateway handler or callback dispatcher exists. Five adjacent modules expose terminal callback receivers, so end-to-end decision propagation remains Partial.
Authoritative totals
| Artifact | Verified total | Maturity |
|---|---|---|
| Workflow domain-event types | 6 | Implemented |
| Workflow integration-event contracts | 6 | Implemented/Partial delivery |
| Workflow-specific message contracts | 6 | Foundation |
| Workflow hosted outbox relays | 1 | Implemented |
| Verified Workflow event consumers | 0 | Not implemented |
| Adjacent callback receivers | 5 | Partial |
| Workflow delegation events | 0 | Not implemented |
Documentation map
Start with event overview and architecture. Catalogs cover domain events, integration events, workflow lifecycle, task events, approval, rejection, delegation, publishers, consumers and message contracts.
Integration and delivery pages cover notifications, callbacks, compatibility, outbox, delivery, ordering, correlation, idempotency, retries/failures and timeline versus events. Finish with testing, limitations and source map.
Evidence boundary
Static source was inspected. No broker, API, database, callback, queue or runtime configuration was accessed.
Requires Confirmation
Deployed broker topology, event consumers, callback bridge, notification ownership, retry governance, ordering, replay and operational monitoring require confirmation.
Source References
microservices/src/workflow-service/Domain/Workflow/WorkflowDomainEvents.csmicroservices/src/workflow-service/Messaging/WorkflowIntegrationEvents.csmicroservices/src/workflow-service/Infrastructure/WorkflowDbContext.csmicroservices/src/workflow-service/Messaging/OutboxRelayHostedService.cs
Related Articles
See Also
Keywords
Workflow events, integration contracts, transactional outbox.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20