MSAMM
Back to course

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

Reading an error from a service

Lesson 103 of 176 · 3 min

Turning a FUSION VALIDATION MESSAGE into something in THE USER'S LANGUAGE AND THEIR VOCABULARY. Module 6 Lesson 7 said a write is refused routinely. This is what to do with the refusal, and there are three bad answers before the good one. THE FIRST BAD ANSWER IS SHOWING THE RAW RESPONSE. A structured payload with nested objects and an internal code is not a message; it is evidence that something happened, displayed to somebody who cannot use it. THE SECOND IS REPLACING IT WITH "SOMETHING WENT WRONG". That discards the one genuinely useful thing in the response — Fusion frequently says exactly which attribute and why, and that is the sentence the user needs. THE THIRD, AND THE MOST TEMPTING, IS MAPPING EVERY KNOWN ERROR TO YOUR OWN WORDING. It reads beautifully for the errors you anticipated and produces nothing at all for the ones you did not — and

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