Oracle Visual Builder: Applications That Outlive Their First Release · Module 8 · Action chains and events
What breaks: four action chain failures
Lesson 89 of 176 · 3 min
A DOUBLE SUBMIT THAT CREATED TWO RECORDS, A FAILURE NOBODY WAS TOLD ABOUT, A TWENTY-STEP CHAIN NOBODY COULD CHANGE, and A VALIDATION THE BROWSER SKIPPED. THE DOUBLE SUBMIT IS THE ONE WITH A VISIBLE CONSEQUENCE, AND THE USER DID NOTHING WRONG. No feedback while the call was in flight, a reasonable second press, and two records. Lesson 6, prevented in the browser by disabling the control and prevented properly by a constraint on the server — which is the only one of the two that also covers a retried request. THE FAILURE NOBODY WAS TOLD ABOUT IS THE MOST DAMAGING BECAUSE IT LOOKS LIKE SUCCESS. A chain stops at a failing step, nothing renders, and the user believes the record was saved. Lesson 7, and the absence of an error is doing the harm — a visible failure would have cost thirty seconds. THE TWENTY-STEP CHAIN IS THE SLOW ONE.…
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.
In this module: Module 8 · Action chains and events
- 1What an action chain isFree preview
- 2Events: what can start one
- 3The common actions
- 4Conditions and branching
- 5Chains that call chains
- 6Waiting: asynchronous steps
- 7Failure inside a chain
- 8JavaScript, and when to reach for it
- 9Keeping a chain readable
- 10Debugging one that misbehaves
- 11Logic that does not belong here
- 12What breaks: four action chain failures
- 13Lab briefing · A chain that survives being read