Difference between revisions of "Subscription and Notification Pattern"
| Line 13: | Line 13: | ||
Business Process (picture) | Business Process (picture) | ||
| − | |||
Activity Table (paste) | Activity Table (paste) | ||
| Line 19: | Line 18: | ||
Business Process (picture) | Business Process (picture) | ||
| + | Activity (paste) | ||
| − | + | === Process Realization === | |
| + | ?All on one Page or do we create sub-pages for Business Process and Process Realization? | ||
== Used by the following use cases == | == Used by the following use cases == | ||
Revision as of 09:04, 23 April 2021
Introductory text
Functional Variants of the Subscription and Notification Patterm
Two distinct business requirements for Subscription and Notification Pattern: Updating of previously shared Evidence or being informed about an Event
Technically also two different approaches to Notification: Sending updated Data of a defined Evidence type or Event Notifications that contain only the identification data and the event type. Technical approach and business requirement do not relate one two one, giving rise to potential hybrid approaches.
Event The reference Architecture for the DE4A projects focusses the Subscription and Notification Pattern on Event Notification, which can be combines with the Lookup Pattern to cover the updating previously shared evidence use case.
Business Process
Event Subscription
Business Process (picture)
Activity Table (paste)
Event Notification
Business Process (picture)
Activity (paste)
Process Realization
?All on one Page or do we create sub-pages for Business Process and Process Realization?
Used by the following use cases
Application collaborations
TBD