MSAMM
Back to course

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

Field-level and form-level

Lesson 101 of 176 · 3 min

What to check AS SOMEBODY TYPES and what to check WHEN THEY SUBMIT. Getting this backwards is WHY FORMS FEEL HOSTILE. The two are not interchangeable, and the difference is entirely about when a rule can fairly be applied to someone mid-task. THE HOSTILE FORM IS THE ONE THAT VALIDATES A FIELD BEFORE THE PERSON HAS FINISHED WITH IT. Type the first character of an email address and be told it is invalid. Enter one digit of a phone number and see a red message. Every one of those complaints is technically correct and arrives while the user is doing exactly the right thing. SO FIELD-LEVEL VALIDATION SHOULD FIRE ON LEAVING THE FIELD, NOT ON EACH KEYSTROKE. Leaving is the signal that the person considers it finished. The exception is a field with a live constraint the user needs while typing — a character counter approaching a limit — 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