Output messages are pieces of textual information the Smart Client wants to present to the user to keep the user informed about the actions of the Smart Client, the Application Server or other parts of the Redbex software system. For example output messages are used to display messages included in the result of a service request to the Application Server (server feedback messages).
The Smart Client has different possibilities to show Output messages. The Output Message window is the central place where all issued output messages will be displayed. The Status bar displays only the last view issued issued message.
Display |
Usage |
Output Messages window |
All issued output messages are shown in the Output Messages window |
Status bar |
The status bar shows only the last issued message and shows the last 5 issued messages in a popup when the mouse hovers over the status bar. |
Info window |
Output messages with an interruptiveness of Draw attention are displayed as non-modal info window. |
Table 1: Different displays of output message and their usage.
Property |
Description |
Source |
The source that originally issued the message. Possible values are: •Application Server •Smart Client |
Severity |
Severity of the message. Possible values are •Information: Information that might be useful for the user. •Warning: Information about an event that is important for the user. •Error: Information that tells the user that something did not work as expected. |
Interruptiveness |
The interruptiveness defines how "interruptive" the message shall be. Note that severity and display priority are not the same. There might be a message with low severity that should still be highly interruptive. The other way round a message might have hight severity but low display priority. Following display priorities are supported: Do not disturb Draw attention |
Timestamp |
The date and time when the message was issued |
Message text |
The message text |
Action log |
Optionally a message can include an action log that gives more details to the user. |
Actions |
An output message might contain actions that the user can trigger. |
Table 2: Properties of an output message
