Button labels should always be short and succinct. The following table contains examples of good and bad button labels:
| Good | Bad |
|---|---|
| Lines | Enter Order Lines |
| Run Print Report | |
| Margins | Set Document Margins |
| Apply Notes | Automatically Apply Notes |
(OMS-75012) Ellipsis points (...) are used at the end of a menu entry or button label in the following cases:
The entry or button opens a modal window (for example, the menu entry "About Oracle Applications...".
The user needs to provide further information about the action in another window (modal or not) before the action can be completed.
Button examples with ellipses:
Copy to...
Find Exceptions...
(OMS-75029) Ellipsis points should not be used at the end of a menu entry or button label if:
the button is used to open a non-modal window that does not require further information before the current action can be completed.
the button or menu entry opens a confirmation window because it invokes a potentially destructive or irreversible action, but does not require additional information to carry out its function.
(OMS-75013) Do not include the word "Percent" in the prompt - always use the symbol "%".
In any case where the percent sign is used, do not enclose it in parentheses or any other delimiters.
(OMS-75014) Single-record percent fields should have the prompt before the field and a percent sign as boilerplate immediately after the field (no gap).
In this case, Hint Text must be added to the field, like "Prompt %".
(OMS-75015) Multi-record fields have a prompt above the field such as "Prompt %":
If the only reasonable prompt is "Percent," then only use "%" after the field or above the column. This occurs when the qualifying word is part of the region title.
Hint Text for these fields must be "Quota To Date: Total" and "Quota To Date: %".
(OMS-75030) The data in a percent field should always be right-aligned.
Percent fields should specify range limits of 0 to 100 if appropriate.
(OMS-75031) Use the terms "From" and "To" to identify fields involved in a range rather than "Start" and "End" or "Low" and "High."
Note: If there is a standard industry term that is more appropriate for your product, use it instead of the generic "From" and "To" terminology. You may alternatively place the range fields horizontally with a single prompt (such as "Hire Dates") in front of the "From" field and a dash between the fields as in "Hire Dates _____ - ____" instead of spelling out the prompts From and To.
For the second field, Hint Text must be provided, such as "Hire Dates: To."