Oracle Visual Builder: Applications That Outlive Their First Release · Module 10 · Validation and error handling
Failing without losing the work
Lesson 105 of 176 · 3 min
A save that failed SHOULD NOT EMPTY THE FORM. What to keep, and THE USER WHO TYPED IT ALL TWICE. This is the cheapest fix in the module — it is usually a matter of not doing something — and it is the failure users resent most. THE MECHANISM IS ALMOST ALWAYS A CHAIN THAT RESETS OR RELOADS ON THE WAY OUT. Written for the success path, where clearing the form is correct, and reached on failure too because the exit is shared. Nobody decided to discard the work; the chain simply did not distinguish the two endings. WHAT TO KEEP IS EVERYTHING THE USER TYPED, EXACTLY AS THEY TYPED IT. Including the value that was rejected — especially that one, because it is the one they need to correct, and clearing it removes the evidence of what they got wrong. WHAT TO RESTORE IS EVERYTHING THE CHAIN CHANGED ON…
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.