MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 10 · Validation and error handling

Errors in Arabic

Lesson 104 of 176 · 3 min

BOTH LANGUAGES, BOTH DIRECTIONS, and THE MESSAGE THAT CAME BACK FROM THE SERVER IN ONE OF THEM ONLY. Module 7 Lesson 5 covered the page. Errors are harder, because half of them are written by you and half arrive from somewhere else. YOUR OWN MESSAGES ARE THE EASY HALF AND STILL HAVE TWO TRAPS. They must exist in both languages, which means writing them as translatable text rather than as literals in a chain — a message assembled by concatenating a label and a phrase produces word order that is wrong in one of the two, so the whole sentence must be translatable, not its pieces. AND ANY NUMBER IN AN ERROR IS THE NUMERAL TRAP AGAIN. "Must be at most 500 characters" carries a quantity, and it needs formatting like every other number — Module 7 Lesson 5, in the place people least expect it. THE SERVER MESSAGE IS

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 10 · Validation and error handling

  1. 1Where validation can live
  2. 2Client-side validation is a courtesyFree preview
  3. 3Field-level and form-level
  4. 4Messages a user can act on
  5. 5Reading an error from a service
  6. 6Errors in Arabic
  7. 7Failing without losing the work
  8. 8Logging, for somebody who is not there
  9. 9What breaks: three validation failures