| Message Pattern Set |
| Warning | Version 2.0.0.0 |
||
|
|||
| Description | |
Warning messages tell users about important immediate or future consequences of data, user interface (UI) action, business rule validation, or requested processes.Warning messages also call attention to any intended or impending action on the user's or the application's part that could have potentially destructive or irreversible consequences. A warning message may also ask users a direct question, asking them to decide between a choice of actions before they can proceed. This question stops the taskflow until the user responds. Warning messages may be at the component (and therefore list) or page level, shown either as dialog boxes or inline on the page. Inline messages are set using the inline attribute on the Application Development Framework (ADF) af:messages component. If a question is required, the message must be in a dialog box. Important: A page cannot contain a combination of inline or dialog box-based messages. The choice is determined at the page level by the ADF af:messages component, which allows only one type on each page. Individual messages on the page use the af:message component. Warning message dialog boxes are modal in cases where users must respond to the warning message by choosing an action in response to a question. |
| Pattern Set Decision Table | |
Warning |
|||||
Tells users that the data they entered in a field violates a business, UI, or formatting rule, and explains how to correct the error. |
Yes |
No |
No |
No |
No |
Tells users about important consequences of a validation of a UI or business rule, or a process execution, that they must be aware of either now or later in the taskflow. Or Tells users about potentially dangerous or destructive consequences of their action, or the application's progress. May include a direct question asking users to decide between alternative actions before proceeding with their task. |
No |
Yes |
No |
No |
No |
Tells users about the status or changes of a business object, a page, or the application itself that was not initiated by the users and does not require any immediate action to be taken by them. |
No |
No |
Yes |
No |
No |
| Tells users about the progress of an action or a process that they or the application initiated. | No |
No |
No |
Yes |
No |
| Tells users when an action or process that they or the application initiated has completed. | No |
No |
No |
No |
Yes |
| Pattern Sample |
| Component and List Inline Warning Message | |||||||||||||||
Component and List Dialog Box Warning Message When users perform a page action, warnings are listed in a modeless dialog box. Components with warnings are outlined with yellow borders. Focus is given to each editable field individually at the component level from the listed components. The dialog box also enables the user to navigate to other component-level messages or to return to the list in the dialog box using the All button.
Components Required Page-Level Warning Message Warnings may appear at the page level, either in a dialog box or inline on the page. This page-level warning appears when a payment batch is created, informing users which invoice terms will be used for the process.
This dialog box-based warning message informs users about how a budget adjustment will be calculated for a project.
Components Required Page-Level Warning Message with Decision Point Warning messages may offer users a decision point in the form of a question that is part of the message. Questions are asked using a page-level dialog box only; questions are not supported at the component or list level. Users must choose between options in the dialog box, presented as action buttons. See the Buttons Usage Guidelines for more information. These dialog boxes are modal, preventing the user from continuing or interacting with the base page without responding to the message dialog box first.
This page-level dialog box tells users that an action cannot be reversed before giving them the option of choosing between actions.
|
| Display Options For Warning Messages |
Warning |
|||||
Component |
Yes |
Yes (without a question) |
Yes |
No |
No |
| List | Yes |
Yes (without a question) |
Yes |
No |
No |
| Page | Yes |
Yes |
Yes |
Yes |
Yes |
| Design Considerations |
Follow the Applications Process Model (APM) collaborative design and implementation process for messages. Messages designed outside this process are not supported by Oracle Fusion Applications User Experience.
|
| Related Guidelines | |
| Messaging Usage Guideline | Guidelines for messages usage based on the Rich Client User Experience (RCUX) designs |
| Oracle Fusion Message Usage Guideline | Guideline about validation across different components in the Oracle Fusion Application's user interface that explains when to use dialog boxes or inline messages |
| Secondary Windows Guideline | Guidelines for the secondary window component |
| Buttons Usage Guideline | Guideline on buttons used for navigation and actions |
| Save Model Guideline | Guideline for designing save model interactions, including warning messages about unsaved data. |
