FusionGPS: Standards and Guidelines: Fusion Message Review Checklist

Fusion Message Review Checklist	Version 2.0.0.0

Contents

Preparation
Related Information

Preparation

a	Read the Message Design Pattern Set and decided on the type of message for the business and user interface (UI) rule required.
b	Read the Message Content Guideline and decided on the components and phrasing needed.
c	Read the Fusion Messages Usage Guideline and established when validation occurs, at what level the message will appear (component or page-level), and how it should be phrased.
d	Read the Fusion Messages Usage Guideline and determined whether the message will be an inline or dialog-based message.
e	Established with the developer and the support team what supportability attributes for the creation of incidents and logs, are required, how they will be raised, and addressed supportability content issues.
f	Completed any translation notes, where required.

1. Error

a	Checked that the message tells users how to fix the error and proceed.
b	Checked that the Application Developer Framework (ADF) is not providing a validator or converter message that eliminates the need for a client-side message to be written for that component.
c	Checked the Message Review Tool for any common message that would be suitable for the business or UI rule.
d	Checked the Fusion Message Text Patterns Guideline for a template to compose a message.

e	Checked the Fusion Message Content Guidelines for guidance about composing a message with tokens.

2. Information

a	Checked that the message tells users about some application, page, or business object status or change that the they did not initiate and that does not require any immediate action on their part in response.
b	Checked the Message Review Tool for any common message that would be suitable for the business or UI rule.
c	Checked the Fusion Message Text Patterns Guidelines for a template to compose a message.
d	Checked the Fusion Message Content Guideline for guidance about composing a message with tokens.

3. Warning

a	Checked that the message tells users about an important data validation or application situation they must know about before proceeding.
b	Checked the Message Review Tool for any common message that would be suitable for the business or UI rule.
c	Checked the Fusion Message Text Patterns Guideline for a template to compose a message.
d	Checked the Fusion Message Content Guideline for guidance about composing a message with tokens.
e	Made a decision on whether the user needs to respond to a question before proceeding (dialog warnings only), or whether the warning is a statement only.
f	Checked that any action buttons provided in response to a question in a warning dialog follow the Rich Client User Experience Buttons Usage Guideline.

4. Processing

a	Checked that the message tells users that an action they performed or process that was scheduled is in progress.
b	Checked the Message Review Tool for any common message that would be suitable for the business or UI rule.
c	Checked the Fusion Message Text Patterns Guideline for a template to compose a message.
d	Checked the Fusion Message Content Guidelines for guidance about composing a message with tokens.
e	Determined any possible use of background processing that won't interrupt the user.

f	Established if the processing is determinate or indeterminate and uses the correct ADF component.

5. Confirmation

a	Checked that the message tells users that an action they initiated (and where no visible confirmation is possible) or a process has completed.
b	Checked the Message Review Tool for any common message that would be suitable for the business or UI rule.
c	Checked the Fusion Message Text Patterns Guideline for a template to compose a message.
d	Checked the Fusion Message Content Guidelines for guidance about composing a message with tokens.

6. Back-end Messages

a	Reviewed the text and decided on appropriate use of passive voice and delimiters.
b	Checked that there is no concatenation of phrases at run-time.
c	Removed any symbols or formatting marks from the text.
d	Confirmed that the message will display and print from the back end.
e	Checked the Fusion Message Content Guidelines for guidance about composing a message with tokens.
f	Ensured that the text is not being used in reports, enterprise scheduler logs, WebCenter Activity Streams, strings on UI pages, or as status icon text.


7. Additional Checkpoints

a	Messages are not used as a workaround for poor design and usability.
b	Messages do not overlap with or conflict with any embedded help provided in the task flow.
c	Messages appear at the points of interaction or data validation when they are needed.
d	Back-end, error, or warning messages enable the user to get to the source of the error in the UI and fix it by referring to the UI component by name when the message cannot automatically give focus to the point of the error.
e	Message text follows the content guidelines.

Related Information