Difference between revisions of "EProcedure Back-office Backend"
Jump to navigation
Jump to search
| Line 39: | Line 39: | ||
|Event Evaluation | |Event Evaluation | ||
| | | | ||
| + | |||
| + | |||
| + | The notified event is analysed and the appropriate response is determined. | ||
| + | |||
| + | Depenting on the event, different courses of action are possible (see details below): | ||
| + | |||
| + | * Event is not relevant | ||
| + | * Event requires a new (i.e. updated) evidence | ||
| + | * Business response required | ||
| + | * Exception: The notification does not match the record or the record is not active, hence the subscription needs to be changes (i.e. cancelled) | ||
| + | |||
| + | The determination result is logged as a part of the audit trail: | ||
| + | |||
| + | * Subject identifier | ||
| + | * Notified event | ||
| + | * Request id | ||
| + | * Determined response | ||
| + | * Timestamp of determination | ||
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
Revision as of 11:39, 4 June 2021
| Item | Description |
|---|---|
| name | eProcedure Back-office Backend |
| description | TODO |
| pattern(s) | S&N |
| application collaboration | EProcedure Back-office |
| Application Service | Description | Pattern |
|---|---|---|
| Subscription Initiation | S&N | |
| Update Subscription Log | S&N | |
| Event Evaluation |
Depenting on the event, different courses of action are possible (see details below):
The determination result is logged as a part of the audit trail:
|
S&N |
| Update Notification Response Log | S&N |
| Component | Source | UC | Description |
|---|---|---|---|
| xyz | descr xyz | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| abc | descr abc | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |