MSAMM
Back to course

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

Messages a user can act on

Lesson 102 of 176 · 3 min

WHAT WENT WRONG, and WHAT TO DO ABOUT IT. An error that only NAMES A FIELD has done HALF THE JOB. A message that stops somebody and does not tell them how to continue has converted a small mistake into a support call, which is the whole subject of this lesson. THE THREE PARTS OF A USABLE MESSAGE ARE WHICH FIELD, WHAT IS WRONG, AND WHAT WOULD BE RIGHT. Most messages carry the first, some carry the second, and the third is what actually unblocks the person. "INVALID DATE" IS THE CANONICAL BAD ONE, AND IT IS BAD IN A SPECIFIC WAY. It says something is wrong and gives no way to work out what — is the format wrong, is it in the past, is it after another date? The user tries three things and one of them works, and they still do not know why. "THE COMPLETION DATE

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
Messages a user can act on — Oracle Visual Builder: Applications That Outlive Their First Release — MSAMM