FusionGPS: Design Patterns: Message Pattern Set: Warning

Warning

Version 2.0.0.0

Message Pattern Set


Description

Warning messages tell users about important immediate or future consequences of data, UI, or business rule validation, or a process requested. 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 to decide between a choice of actions before they can proceed. This question stops the task flow until the user responds.

Warning messages may be at the component (and therefore list) or page level, shown either as dialogs or inline on the page. Inline messages are set using the inline attribute on the ADF af:messages component. If a question is required, the message must be in a dialog.

Important: A page cannot contain a combination of inline or dialog-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 dialogs 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

	Error	Warning	Information	Processing	Confirmation
Tells users that the data they entered in a field violates a business, UI, or formatting rule, and explains how to correct the error. Or Tells users that an application error has occurred that was not due to their action, and that correcting the error will require help desk intervention.	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 task flow. 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, 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

When users perform a page action, warnings are listed at the top of the page. Components with warnings are outlined with yellow borders. Focus is given to each editable field individually at the component level from the listed components, or directly. The component-level note window enables users to also navigate to other component-level messages.

Inline List Showing All Messages (Error and Warning Messages, in Order of Severity)

Figure 1: Inline List Showing All Messages (Error and Warning Messages, in Order of Severity)

Component-Level Warning Message

Figure 2: Component-Level Warning Message

Component and List Dialog Warning Message

When users perform a page action, warnings are listed in a modeless dialog. Components with warnings are outlined with yellow borders. Focus is given to each editable field individually at the component level from the listed components. This also enables the user to navigate to other component-level messages as well as to return to the list in the dialog using the All button.

Component-level Warning Message

Figure 3: Component-level Warning Message

Components Required

Required Screen Elements for Message List Warnings
Component Type	Required Components			Customizable/Extendable Components
Message Icon		warning_qualifier.png	The warning icon precedes the message title. If there is a mix of message types in the list, then the icons and titles reflect the order of severity. Errors are always listed first.	Not applicable
Message Title	Format is: Warning
Message Region	The message content contains: Introductory message: This is provided by ADF. Teams should not change this message: Messages for this page are listed below. Component name: A link to the name of the component. The component ID should be used to ensure the name of the link matches the name of the component. Warning qualifier icon. Message summary: A short description of each warning taken from the Message Text component. The format is: Warning message text. (Error Code) (The error code is optional depending on the support requirements for the business rule.) Message User or Admin Detail: Optional additional details intended for end users or administrative users. Message Cause: Optional cause of the warning message. Message User Action or Admin Action: Optional action required to be taken by end users or administrative users to resolve the message.			Not applicable
Dialog Buttons	Iconic close icon: Clicking this icon closes the dialog. OK: Clicking this button closes the dialog.			Not applicable
ADF Component	af:messages			Not applicable

Required Screen Elements for Component Warnings
Component Type	Required Components			Customizable/Extendable Components
Note Icon		warning_qualifier.png	The warning icon precedes the note title.	Not applicable
Note Title	Format is: Warning
Note Region	The message content contains: Message summary: A short description of each warning taken from the Message Text component. The format is: Warning message text. (Error Code) (The error code is optional depending on the support requirements for the business rule.) Message User or Admin Detail: Optional additional details intended for end users or administrative users. Message Cause: Optional cause of the warning message. Message User Action or Admin Action: Optional action required to be taken by end users or administrative users to resolve the message.			Not applicable
Note Buttons	Traversal and All buttons appear if more than one component message is active.
ADF Component	af:message			Not applicable

Page Level Warning Message

Warnings may be shown at page-level, either in a dialog 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.

Page-level Inline Warning Message

Figure 4: Page-level Inline Warning Message

This dialog-based warning message informs users about how a budget adjustment will be calculated for a project.

Page-level Warning Message Dialog

Figure 5: Page-level Warning Message Dialog

Components Required

Required Screen Elements for Page-level Warnings
Component Type	Required Components			Customizable/Extendable Components
Message Icon		warning_qualifier.png	The warning icon precedes the message title.	Not applicable
Message Title	Format is: Warning
Message Region	The message content contains: Message summary: A short description of each warning taken from the Message Text component. The format is: Warning message text. (Error Code) (The error code is optional depending on the support requirements for the business rule.) Message User or Admin Detail: Optional additional details intended for end users or administrative users. Message Cause: Optional cause of the warning message. Message User Action or Admin Action: Optional action required to be taken by end users or administrative users to resolve the message.			Not applicable
Dialog Buttons	Iconic close icon: Clicking this icon closes the dialog. OK: Clicking this button closes the dialog.			Not applicable
ADF Component	af:messages			Not applicable

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 only; questions are not supported at component or list level. Users must choose between options in the dialog, presented as action buttons. See the RCUX Buttons Usage Guidelines for more information. These dialogs are modal, preventing the user from continuing or interacting with the base page without responding to the message dialog first.

This page-level dialog tells users an that action cannot be reversed before giving them the option of choosing between actions.

Page-level Warning Message Dialog with Decision Point and Action Buttons

Figure 6: Page-level Warning Message Dialog with Decision Point and Action Buttons

In Fusion 1.0, the only patternized decision-point warning message took the standard "Do you want to continue?" followed by a "Yes" or "No" response. Post-Fusion 1.0, teams may use other combinations of questions and action buttons in the message dialog.

Page-level Warning Message Dialog with Decision Point and Yes and No Buttons

Figure 7: Page-level Warning Message Dialog with Decision Point and Yes and No Buttons

Required Screen Elements for Page-level Warnings with Decision Point
Component Type	Required Components			Customizable/Extendable Components
Dialog Icon		warning_qualifier.png	The warning icon precedes the dialog title.	Not applicable
Dialog Title	Format is: Warning
Dialog Region	The message content contains: Message summary: A short description of each warning taken from the Message Text component. The format is: Warning message text. (Error Code) (The error code is optional depending on the support requirements for the business rule.) Message User or Admin Detail: Optional additional details intended for end users or administrative users. Message Cause: Optional cause of the warning message. Message User Action or Admin Action: Optional action required to be taken by end users or administrative users to resolve the message.			Not applicable
Dialog Buttons	Iconic close icon: Clicking this icon closes the dialog. Action buttons.			Yes. Teams can add action buttons in response to questions.
ADF Component	af:messages			Not applicable

Display Options For Warning Messages

	Error	Warning	Information	Processing	Confirmation
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 APM's collaborative design and implementation process for messages. Messages designed outside this process are not supported by Apps-UX.
Use the Fusion Message Content Guidelines for designing and reviewing message text.
Refer to the Fusion Message Usage Guideline for guidance about when to use dialog or inline messages and about validation across different components.

Related Guidelines

RCUX Messaging Usage Guideline	Guidelines for messages usage based on the RCUX designs.
ADF Component Guide	Demonstrations of af:message, af:messages, validators and converters components.
Fusion Message Usage Guideline	Guideline about validation across different components in the Oracle Fusion Application's user interface that explains when to use dialog or inline messages.
RCUX Secondary Windows Guideline	Guidelines for the secondary window component.
RCUX Buttons Usage Guideline	Guideline on buttons used for navigation and actions.