Difference between revisions of "EProcedure Back-office Front-end"
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
|- | |- | ||
| Notification Mismatch Signal | | Notification Mismatch Signal | ||
| − | | | + | | When the company cannot be identified or the registered company or branch is no longer active a change (i.e. cancellation) of the subscription is requested. Afterwards this will be analysed to find the cause of this apparently wrong subscription and to take appropriate measures. This subprocess includes user tasks ad is not end-to-end automated. |
| [[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 Front-end |
| description | TODO |
| pattern(s) | S&N |
| application collaboration | EProcedure Back-office |
| Application Service | Description | Pattern |
|---|---|---|
| Notification Mismatch Signal | When the company cannot be identified or the registered company or branch is no longer active a change (i.e. cancellation) of the subscription is requested. Afterwards this will be analysed to find the cause of this apparently wrong subscription and to take appropriate measures. This subprocess includes user tasks ad is not end-to-end automated. | 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. |