Message Pattern Set Version 2.0.0.0Print this Page
 
 
Description
Return to Top

Oracle Fusion Applications is optimized for ease-of-task completion and user productivity. To achieve this, users must be told about business rule errors (such as missing or incorrect data) and how to resolve these errors; warned about the consequences of intended actions; informed about the status of the application, pages, and business objects; and assured that processes and actions are performing and when they are completed.

Oracle Fusion Applications messages provide for these requirements. This message pattern set includes patterns for designing confirmation, error, information, processing, and warning messages. These messages are designed to meet the business and user interface (UI) rule requirements identified in the functional design phase of the Applications Process Model (APM).

The patterns in this set describe the visual treatment and interaction of the messages within the application and are based on the Rich Client User Experience (RCUX) visual designs and the Application Development Framework (ADF) components.

Patterns are not prototypes or content guidelines, and the examples shown are intended to illustrate only the visual specification and interaction afforded when a message is called by the application.

To support messages on table rows, master detail objects, across tabs, read-only pages, and other components not in the patterns, product teams should refer to the Fusion Message Usage Guideline.

A "Do not show this message again" style of message is not supported by these message patterns or by application end-user preference.

Patterns to Create Messages
Return to Top

Error

A message that tells users about incorrect data or formats when they complete a field, save a page, or perform any other UI action that triggers validation and explains how users can correct the situation.

This message also tells users about any serious problem with the application or process that has occurred without their input and that they cannot recover from without help desk intervention.

Warning

A message that tells users about important consequences of a UI or business rule validation or any executed process that they must be aware of, either now or later, in the taskflow.

This message can also prompt users to make a decision about alternative actions before proceeding with their tasks.

Information A message that tells users about a business object, page, or application status or change not caused by the users but that they may need to know about. These changes require no immediate action from the users.
Processing A message that tells users that a requested action or process is in progress.
Confirmation A message that tells users that an action or process that they or the application requested has completed.

 

Pattern Set Decision Table
Return to Top
 

Error

Warning

Information

Processing

Confirmation

Tells users that the data that they entered in a field violates a business, UI, or formatting rule. Explains how to correct the error.

Or

Tells users that an application error has occurred that was not due to their actions and that correcting 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 actions or the application's progress.

May include a direct question asking users to decide between alternative actions before proceeding with their tasks.

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

 

How Messages Appear to the User
Return to Top

Depending on the type of message and validation invoked, Oracle Fusion Applications messages appear to the users in different ways: by component, in a list, or by page. Use the Messages Display Options table for a summary, by type, of the different ways that messages can appear.

Messages can also appear in dialog boxes or inline. Inline messages are set using the inline attribute on the af:messages component. See the Oracle Fusion Message Usage Guideline for a decision table explaining how to decide between the two options.

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.

With the exception of application errors, some warnings, and processing messages, all dialog boxes are generally modeless. The ways that messages can appear is summarized in this document.

Component

The Application Development Framework (ADF) provides for simple, client-side error messages used through converter and validator components . These components provide their own message in a note window, shown when users tab out of an editable field without having provided, or corrected, data.

Product teams must design and build other validations and provide messages for their product's business and UI rules.

ADF Validator Error Message in Note Window
Figure 1. ADF Validator error message in note window

Component messages appear in a note window and activated when users tab out of an editable field. Components with errors are outlined with red borders. Components with warnings are outlined with yellow borders.

Component Error Message in Note Window
Figure 2. Component error message in note window
When there is more than one component message on a page, the note window also enables users to navigate to other messages or to show all messages in a list using the traversal and All buttons. At present, users cannot scroll back to the top of the page to show all inline messages again using the All button in a component message .

List

A list is a summation of all the component-level messages for that page. Different types of messages appear together, in order of severity. See the Message Display Options for supported types. Generated links in the dialog box or on the page, using the name of the component, enable users to give focus directly to each individual component with a message. Lists generally appear when users perform a page-level action or complete a heads-down action.

Page

Page-level messages appear using a message dialog box or appear inline on the page. These page-level messages are generally used in the following scenarios:

  • For business rules validation where no component-level validation can be performed.
  • When component-level validation would impact application performance.
  • For page-level actions (saving, publishing, and so on) taken after component-level messages are resolved.
  • When a process is running or confirmed.
  • For serious errors and warnings concerning the application. A page-level message dialog box ensures that the user's attention is caught in these cases.

The following are examples of how messages appear(details on the designs and interactions are in the Messaging Usage Guideline):

 

Pattern Sample
Return to Top

Component and Inline List Messages

All messages for the page appear in a list on the page. Components with errors and warnings are outlined with red and yellow borders, respectively. At present, messages appear only at the top of the page . Users fix each component-level issue individually by giving focus to the component from the list or directly.

Error Message Listed Inline
Figure 3. Error messages listed inline
Error Message in Component Note Window
Figure 4. Error message in component note window

Component and Dialog Box List Messages

All messages for the page appear in a list in a modeless dialog box. Users fix each component-level issue individually by giving focus to the component from the list or directly.

Error Messages Listed in Dialog
Figure 5. Error messages listed in a dialog box
Error Message in Component Note Window
Figure 6. Error message in a component note window

Page-Level Messages

A message appears on the page, inline, or in a dialog box.

Page-level Error Message Inline
Figure 7. Page-level error message inline
Page-level Confirmation Message in Dialog
Figure 8. Page-level confirmation message dialog box
Page-level Warning Message with Decision Point and Action Buttons in Dialog
Figure 9. Page-level warning message dialog box with decision point and action buttons
 
Message Display Options
Return to Top
 

Error

Warning

Processing

Confirmation

Component

Yes Yes Yes No No
List Yes Yes Yes No No
Page Yes Yes Yes Yes Yes
 
Design Considerations
Return to Top
  • Follow APM's collaborative design and implementation process for messages. Messages designed outside this process are not supported by Oracle Fusion Applications User Experience.
  • See the Oracle Fusion Message Usage Guideline for guidance about when to use dialog boxes or inline messages and about validation across different components.
 
Related Guidelines
Return to Top
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
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights