Fusion Message Text Pattern Guideline
Version 2.0.0.0
Introduction
Return to Top

Use these guidelines to create new messages with a consistent user experience. Use each message text pattern to create your own message text, replacing the words within the angle brackets (<>) with your own. The text patterns enable you to develop messages for specific user interactions, saving effort and cost throughout the message life cycle. Teams may also choose to replace words in these text patterns with tokens of their own, modifying any text to accommodate, and sharing the same message within a product area. The tokens shown in these text patterns (in the format of {UPPER_CASE}) must be declared, raised and verified by the product team.

For guidelines about how to extend these text patterns, see the Message Content Guidelines.

Contents
Return to Top
Incorrect Number of Fields Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Field, either/or error, mandatory You must enter a value for either <field type 1> or <field type 2), not both. You must enter an amount or a percentage, not both.
Field, either/or error, not mandatory You can select <field type 1> or <field type 2>, not both. You can select permanent or seasonal position, not both.
Field, one of more of several, mandatory

You must enter a value for <field type 1>, <field type 2>, or <field type 3 >.

You must enter a value for at least one of <field type 1>, <field type 2>, or <field type 3>.

You must enter a value for the customer ID, customer name, or customer number.

For a direct move, you must enter a value for at least one of maximum load weight, pallet floor space, or effective volume capacity.

You must enter a value for labor start time, a labor end time, or an item.

Field, only one of several, mandatory

You must enter a value for only one of <field type 1>, <field type 2>, or <field type 3>.

You must enter a <combination 1> or <combination 2>.

You must enter a value for only one of a price list, a class, a course, or a category.

For a service item, you must enter an end date or a service period plus duration.

Field, only one of several, not mandatory You can enter a value for only one of <field name 1>, <field name 2>, or <field name 3>.
You can enter a value for only one of a person ID, an assignment ID, or an organization ID.
Invalid Range Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Later/greater than error

The <date/object> must be <later/greater> than or equal to {TOKEN} .

The <date/object> must be <later/greater> than {TOKEN}.

The <date/object> must be <later/greater> than <date/object>.

The date must be later than or equal to {TODAY_DATE}.

The last available document number must be greater than or equal to {LAST_AVAIL_DOC_NUM}.

The end date must be later than the start date.

Earlier/less than error

The <date/object> must be <earlier/less> than or equal to {TOKEN}

The <date/object> must be <earlier/less> than {TOKEN}.

The <date/object> must be <earlier/less> than <object>.

The date must be earlier than or equal to {TODAY_DATE}.

The maximum value must be less than or equal to {MAX_VALUE}.

The target price must be less than the bid start price.

Data range (within) error

The <number object> must be within the <object range>.

The <number object> must be within the <object range> of {TOKEN} to {TOKEN}.

The checkbook start number must be within the available document range.

The reporting code must be within the reporting code range of {CHG_MIN_RANGE} to {CHG_MAX_RANGE}.

Data range (between) error The <value> must be between {TOKEN} and {TOKEN}. The number of columns to display must be between {DIS_MIN_VAL} and {DIS_MAX_VAL}.
Date range overlap A <object> with an overlapping date range already exists for this <attribute>. A rate with an overlapping date range already exists for this combination of expenditure type, nonlabor resource, and organization.
Incorrect Information Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Invalid data error

The <object> is invalid <reason>.

The <object> is invalid for this <object><reason>.

The absence type is invalid because this worker is not an employee.

The external source type segment is invalid for this requisition.

Date, accounting error The <date> is not in an open or future period. The account date is not in an open or future period.
Invalid Action Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Delete error

You cannot delete this <object> because you do not have permission.

You cannot delete this <object> because <reason>.

You cannot delete this customer account because you do not have permission.

You cannot delete this purchase order because it is approved.

You cannot delete this file because it is locked.

You cannot delete this payload item because it is referenced by a payload attribute mapping.

Order of Operations error You must <enter/select> a/an <value> before <verb phrase or value>. You must enter a payment amount before you reconcile your payments.

You cannot delete this purchase order because it is approved.

Item in use error Another <item> is using the <object> you are attempting to <action>. Try again later. Another person is updating the definition you are attempting to update. Try again later.
Action invalid for object error

You cannot <action> <this/the selected> <object>.

You cannot <action> the selected <object> because <reason>.

You cannot edit this definition.

You cannot update this event type because it is protected.

Action invalid for one or more objects error

You cannot <action> at least one of the selected <objects>.

This action cannot be performed on at least one of the selected <object>.

You cannot delete at least one of the selected rows.
Missing Information Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Missing data error The <object> does not exist. Enter a valid <object> for this <object>. The purchase order does not exist. Enter a valid purchase order for this supplier.
Missing data, enter or select a value error You must <enter/select> <article+object>.

You must enter a bank account ID.

You must select a template.

Missing data, enable an object error

You must enable the <object>.

You must enable either the <object> or the <object>.

You must enable the supplier.

You must enable either the allow offset taxes option or the set as self assessment option.

Missing value, default used error A/An <value> was not entered. The default <value> will be used instead A supplier site was not entered. The default supplier site will be used instead.
Missing data, set a value error You must set the <value> to <possible values><value>. You must set the payment scheme to a purchase card or bank account option.
Mandatory values error You must enter a/an <value>. You must enter a payment type.
Duplicate Information Errors
Return to Top
Message Use Case Message Text Pattern Example Message
Unique data error The <value> must be unique.

The purchase order number must be unique.

The combination of ledger and business unit must be unique.

Duplicate data error <This/The/A> <object> already exists. This record already exists.
A statement with this bank account number and statement header already exists.
Duplicate value error

A <object> for this <value-type> already exists. Enter a unique <value-type>.

A <object> with the value {VALUE} already exists. Enter a unique value.

A <object> with/for this combination of <values/objects> already exists.

A repeating period with this name already exists. Enter a unique name.

An event definition for this event name already exists. Enter a unique event name.

A construction method for this combination of source object and event definition already exists.

Return to Top
Warnings
Message Use Case Message Text Pattern Example Message
Changes loss warning with confirmation If you <do XYZ>, then you will lose your changes. Do you want to continue? If you cancel, then you will lose your changes. Do you want to continue?
Delete warning with confirmation

The selected <item/type> will be deleted. Do you want to continue?

The selected <item-type> will be deleted. You cannot undo this deletion. Do you want to continue?

The selected account will be deleted. Do you want to continue?

The selected customer will be deleted. You cannot undo this deletion. Do you want to continue?

Downstream dependency warning Changing the <object> also changes the <object>. Changing the exchange rate also changes the reimbursement currency.
Setup warning with confirmation If you <do XYZ>, then your <impacted object, usually setup data> will be  deleted. Do you want to continue?
If you change the budget group segment, then your
existing budget group setups will be deleted. Do you want to continue?

In Fusion 2.0, other combinations of questions and action button responses for the user to decide between may be used in warning messages.

Return to Top
Applications and Failed Operations Errors
Message Use Case Message Text Pattern Example Message
A general application error used at product level (teams should raise an incident/log with this error). The user cannot fix and the cause cannot be determined without help desk intervention.

An application error occurred.

An application error occurred.

An application error occurs that the user cannot fix, with additional detail (teams should raise an incident/log with this error).
Message Text: An application error occurred.
Message User Details: <description of technical error and solution>

An application error occurred.

Records in the table {TABLE_NAME} for primary key
{PRIMARY_VALUE} have effective dates that overlap as of the effective date {SESSION_DATE}.

General failure error for known actions and objects due to an application error (teams should raise an incident/log with this error). An application error occurred with this <object/action>.

An application error occurred with this request.

An application error occurred with this purchase requisition.

Specific failure error that the user needs can fix (no incident/log).

The <object> was not created because <cause>. <Corrective action>.

The <action>failed because <cause>. <Corrective action>.

The purchase order was not created because you do not have permission.

The request for online shipping failed because the shipping information for this customer was not set. Enable the process online option and run the update shipping information concurrent process again.

Action failure error (no incident/log). The <requested action> cannot be <action> because <name the action that is preventing it>. Try again. The information cannot be edited because a report is printing. Try again.

An application-type error occurred that the user did not initiate directly, and can fix by trying again immediately (no incident/log).

For example if a user opens a dialog or switches tabs or launches an LOV, they could trigger this error because it will trigger a db request, but these aren't "requests" from a UI standpoint.

An <object> error occurred. Try again. An application error occurred. Try again.
Application connection errors (teams should raise an incident/log with this error). An application error occurred while establishing a connection to the {SERVER_TYPE} server.

An application error occurred while establishing a connection to the Secured Enterprise Search server.

An application error occurred while establishing a connection to the Content Management server.

Security error (teams should raise an incident/log with this error). You do not have permission to <action> this <object>.

You do not have permission to edit this information.

You do not have permission to delete this member.

An application error occurs that the user cannot fix, with additional detail (teams should raise an incident/log with this error).
Message Text: An application error occurred.
Message User Details: <description of technical error and solution>

An application error occurred.

Records in the table {TABLE_NAME} for primary key
{PRIMARY_VALUE} have effective dates that overlap as of the effective date {SESSION_DATE}.

Confirmations
Return to Top
Message Use Case Message Text Pattern Example Message
Processing confirmation <object> was/has been <verb>.

Expense report IEW2345 for 56 USD has been approved.

Update confirmation <object> was/has been updated. Product description has been updated.
Inactivation confirmation <object> was/has been inactivated. Account has been inactivated.
Creation confirmation <object> was/has been created. Table was created.
Enablement confirmation <object> was/has been enabled. Tax code UK123 was enabled.

Back-end Message Situations

These are messages not associated with ADF components and the Fusion message pattern set and which may be displayed as a text or log output, or product specific UI. See the section on back-end messages in the Message Content Guidelines.

Return to Top
Message Use Case Message Text Pattern Example Message
To support web services and other back-end processing, messages are needed to report when invalid values are provided for attributes.  When data is entered by a user via the UI, these messages wouldn't be needed as the drop down lists, LOVs, or some other UI validation will be used, but the UI validations aren't applicable when the attribute value is obtained through a web service or some other back-end processing.  

(Message text component)   The value provided for the <attribute name> attribute is
invalid.
(User detail component)  Valid values are <specify valid values>.

The value provided for the Approval Required attribute is invalid.
Valid values are Y (yes) or N (no).

The values provided for the Planning Period attribute are invalid.
Valid values for User Defined, Cumulative, and Lead Time. 

Related Information
Return to Top