Error and Alert Messages
Errors are “hard-stops,” or messages that prevent a user from moving forward in their workflow. Alerts, or warnings, are “soft-stops” that convey information a user needs to know to prevent an error, but don’t stop the user from continuing their workflow. In both cases, it’s important to make the content of these messages clear, concise, and useful.
- Write like a human speaks. How would you phrase the error if you were speaking to a friend? Read your error out loud to test how natural your wording sounds.
- Try to tell the user what they need to do to fix the error. Only provide a solution when it is the exact solution that will solve the issue.
- Let the user know what caused the error if that hasn’t been addressed by your fix. Try to balance providing specific information with keeping the message concise.
- Be consistent across messages in the product. Errors of similar types should have similar messages.
Use active voice when writing error messages. You may use passive voice to avoid:
- Assigning fault to a user or 3rd party vendor.
- Negatively reinforcing the Workday brand.
- There was an issue retrieving your information.
- Excellent Enterprise failed to retrieve your information.
However, in the majority of cases, you can keep messages positive, avoid blame, and stay in active voice by telling users what they can do to recover.
- Use short, declarative, complete sentences in present tense.
- Use contractions to make the language more natural and casual.
- End full sentences with periods.
- Don't use special characters such as &, /, quotation marks, and so on. However, you can use tildas (~) for custom labels and brackets ([ ]) for variables.
- Use second person. (“You don’t have permission to access this document.”)
- No need to segue or introduce the error. Don’t use “To fix this error . . .”
- Avoid jargon and technical language. Don’t use value when you mean number.
- Don’t use “please” or “sorry,” but try to keep the tone of the message polite and conversational.
- Don't label any messages with the words “Error” or “Alert.” This information is automatically added to the beginning of error and alert messages.
Don’t include the field label associated with the error in the text of the message. Workday automatically includes a subheading with the corresponding field label hyperlinked above the error message text.
If you directly refer to another UI element (which Workday doesn’t include as a subheading) ensure the name exactly matches what’s in the UI, including capitalization. However, if you refer to UI elements generally, use lower case.
When including variables, try to place them at the end of a message after a colon for ease in translations. Include a noun that will help identify the variable somewhere in the message.
- Enter a valid user. This user isn’t valid: [variable].
Try to limit variables and custom labels to only 1 or 2 per message, if possible. Overuse can lead to confusing messages.
- Select a remit-from ~sponsor~ that isn't already in use for at least 1 other ~sponsor~.
- You cannot select a remit-from ~sponsor~ for this ~sponsor~ because it is the remit-from ~sponsor~ for at least 1 other ~sponsor~.
|You can't close the position if the job is available for overlap.||Close Position cannot be true if the job is available for overlap.|
|Select 1 instant messenger type as Primary.||One and only one instant messenger must be marked as Primary.|
|Enter corrected amounts before you submit.||You cannot submit this time off request as you have not corrected any time off entries. Please enter an updated corrected request and submit the correction again.|
|The worker has pending actions that conflict with this one. Complete the listed actions before starting the new action.||You cannot initiate this action because there are other pending actions for the worker that conflict with this one. Close the pending actions listed below before initiating the new action.|
|Enter an End Date that's in the future.||The End Date must be after today.|
|Enter a Currency ID that isn't already in use.||The Currency ID entered has already been used.|
|Enter an As of Date that's on or after the first eligible period start date.||As of Date must be greater than or equal to the first eligible period start date.|
|Enter an Issue Date [issue date] that's on or before the expiration date [exp date].||Issue date ([issue date]) cannot be after the expiration date ([exp date]).|
|Use a table for the selected element in this function: [variable].||Function [variable] selected element did not contain a table.|
|Enter a valid date for the Expense Report Date field.||Error - Expense Report Date|
|We can't find the page you're looking for.||Page Not Found|
Can't Find What You Need?
Check out our FAQ section which may help you find the information you're looking for.FAQ Section