MSAMM
Back to course

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

What breaks: three validation failures

Lesson 107 of 176 · 3 min

A RULE ENFORCED ONLY IN THE BROWSER, AN ERROR MESSAGE NAMING A FIELD THE USER CANNOT SEE, and A FAILED SAVE THAT CLEARED THE FORM. THE BROWSER-ONLY RULE IS THE ONE WITH THE HIGHEST STAKES AND THE LOWEST VISIBILITY. A validation written carefully in a chain, tested thoroughly through the application, correct on every path a user takes — and absent the moment the endpoint is called directly. Lessons 1 and 2, and no amount of testing the application can find it, because the application is the one thing that goes through the check. THE DAMAGE IS DATA THAT NO SCREEN COULD HAVE PRODUCED. A record violating a rule everybody believes is enforced, discovered downstream by a report that does not balance or a process that refuses to run — and the investigation starts at the report rather than at the missing constraint. THE MESSAGE NAMING AN INVISIBLE FIELD 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.

See the course and enrol9 free lessons

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