Pattern Library/Messages
Jump to navigation
Jump to search
| APPLICATION AREAS |
|---|
|
|
| PROJECTS |
|
Research- and Metadata Handling Corporate & Interface Design (under Rework) |
| edit |
Message Types and Use
If possible, a single line message should appear in the status line position.
Single line messages in red and green can go into the message line, because the user already knows where the system drops a message. So he does not need to look for a different position.| User Concern | Type | Importance | Workflow | Single/Multiline | Color | Border | Example |
|---|---|---|---|---|---|---|---|
| User is infromed about what is displayed and what ist the current status of the system | Info | Useful, but can be ignored | Not affected | Single | Black | None | 108 Items (descending sorted by Modification Date) |
| User needs to provide/correct something for the system to fulfil the task | Error | Critical, can not be ignored | Affected | Multiline | Red | Yes | |
| The system has done something wrong, but can continue | Warning | Only important if work is lost | Not affected | Single | Red | Yes | |
| The system has done something wrong and stops working | Error | Important, because all further work is lost | Affected | Multiline | Red | Yes | |
| The user has completed his work successfully and everything is fine | Success | Important, because user is finished | Affected | Single | Green | No |