The Backend has the opportunity to trigger UI-Messages, which are created/triggered in the backend as part of the Businesslogic, but are displayed in the UI. This allows easier migration of old logic, where data access and UI were not separated.
There are 2 basic types: Messages and Questions.
...
Typical methods that contain code for creating ui-messages:
- Validate
Overview
| Type | visualizationj Sub-types | Transaction update behaviour | UI behaviour | Visualisation Modal/Non-Modal | Sample backend code |
|---|---|---|---|---|---|
| QuestionQuestions | Info / warning / error (?)Cancel | while questions pending it will always undo, when all questions answered it depends on answers and/or the business-logic | Show question, after user clicks button, re-perform backend call, unless user pressed cancel | M | |
| (Messages) | |||||
| Information- Info-Message | Info / warning | Commit | Show message | M (?) / N | |
- Validation-Message | Info / warning / error | Cancelundo | Show validation message | M / N | |
| - Runtime-Error | error | undo | show error message, in a promise (e.g. BusinessTask) the FAIL path will be executed | M / N |