MSAMM
Back to course

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

Client-side validation is a courtesy

Lesson 100 of 176 · 3 min · Free preview

IT MAKES THE FORM PLEASANT. IT STOPS NOTHING, because the request can be made WITHOUT YOUR PAGE AT ALL. Module 11 is the consequence. This is a free preview lesson because it is the sentence somebody should read before deciding this course is about drag and drop. THE MECHANISM IS PLAIN AND NOT A SECRET. Your page calls an endpoint. The endpoint is visible in the browser's own network tab, on the page the user is looking at. Anybody who can open that page can see the URL, the shape of the body, and the credential the browser is sending — and can send their own request. SO EVERY CHECK IN YOUR FORM IS SOMETHING THAT HAPPENS BEFORE A REQUEST YOUR APPLICATION CHOOSES TO MAKE. Skip the page, and the checks never ran — not because they failed, but because they were never in the path. WHICH IS NOT AN

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

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