Error messages communicate essential information, alerts, and warnings of critical problems. They also contain descriptions, solutions, and detailed information, when available.
The error message dialog comprises the following sections:
An icon. One of three icons may be displayed, symbolizing a message type. The usage and descriptions of these icons adhere to Microsoft standards as follows:
Provides information about results of a command. Offers no user choices; the user acknowledges the message by clicking the OK button.
Alerts the user to a condition or situation that requires the user’s decision and input before proceeding, such as an impending action with potentially destructive, irreversible consequences. The message can be in the form of a question; for example: “Save changes to MyReport?”
Informs the user of a serious problem that requires intervention or correction before work can continue.
A short message. The message is as specific as possible and never misleading; for example:
Failed to connect to server.
A remedy. If possible, the remedy includes information that tells the user what to check: for example: Verify:
network connections, server is running, application name is valid, database name is valid.
Details about the error. Click the Show Details button to view available detail information; for example:
ErrorStack: com.hyperion.reporting.util. HyperionReportException: Error getting Datasource Connection at com.hyperion.reporting.client.DesignerManager. getDatasourceConnection(Unknown Source) at com.hyperion.reporting.javacom. DesignerManagerComImpl.getDatasourceConnection(Unknown Source