...
Goals
Magnolia informs me adequatelythe user, if an action I take he started caused an error or requires me him to note read a warning or other textual message. It is especially important to me that I especially don't miss error messages of long running actions aren't missed. If I leave my desk and return, I the users has left his desk, he should either still see all messages when he returns or have find a notification waiting for me informing me that I need to take a look at a him that he should consult the message log, since new important messages have arrived in my during his absence.
Last but not least, all All messages should be non-technical and easy to understand. I should It shall be able easy to copy&paste them if I need customer he intends to contact product support. For the same reason, I'd also like to be able to send my current it must be easy to send the entire message log to support using over a secure channel.
...
Concept
System messages differ from e.g. validation messages in a number of ways. First, they report important system status changes. As such, they have to be displayed more prominently, but should also be used scarcely. Second, the context of a system message is usually gone once it's being shown. As an example, a process running a longer time might fail eventually, or a regular background cleanup job has discovered an oddity, which requires a warning to be displayed to the user. The message thus shows up in any context. By contrast, a validation message can still be visually related to the field, which caused the problem, when it is displayed.
...