-
Feature
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
None
-
False
-
2022 Week 32-34 (from Aug 8)
Motivation
Knative Eventing is a serverless platform that enables developers to create event producers and consumers for their applications. Knative Eventing uses standard HTTP POST requests to send and receive events between event producers and consumers. These events conform to the CloudEvents specification, which enables creating, parsing, sending, and receiving events in any programming language.
Goal
Enable events to trigger specific workflows based on its payload
Scenarios
As a developer, I need to address workflow(s) via domain-specific values in data when sending an event so that the event is consumed only by active workflows which contain that domain-specific value in data.
Expected outcomes
Workflow instances are correlated with incoming events via workflow identifier or workflow data
Correlation attributes are set only using events, i.e. a workflow instance has to have event state as a start
Correlation of events (between events) is out of scope - that’s for complex event processing
Setting correlation attributes using a REST request (e.g. when the operation state is a start) is out of scope
- incorporates
-
KOGITO-6729 SW Events Correlation Implementation
- Resolved
-
KOGITO-3920 [SW] Review `correlationId` implementation for events on SW
- Resolved
-
KOGITO-6784 Incorporate correlation support in kogito process runtime
- Resolved
-
KOGITO-6971 Serverless Workflow Correlation example with Callback
- Resolved
-
KOGITO-7288 [KSW-Guides] Event correlation with workflows
- Resolved
-
KOGITO-6783 Enhance PostgreSQL persistence addon to support correlation
- Resolved
-
KOGITO-6991 Saga Serverless Workflow example with persistence and correlation
- Closed
- is related to
-
SRVLOGIC-20 [core] Data correlation for workflows without event state start
- New
- relates to
-
SRVLOGIC-14 [use case] Event-driven workflows in Knative Eventing platform
- Closed