Oracle Visual Builder: Applications That Outlive Their First Release · Module 8 · Action chains and events
Keeping a chain readable
Lesson 86 of 176 · 3 min
Naming, size, and THE POINT AT WHICH ONE CHAIN SHOULD BE TWO. A TWENTY-STEP CHAIN IS A FUNCTION NOBODY WILL READ. Chains grow the way functions grow: one step at a time, each addition reasonable, and nobody notices the moment it became unreadable. NAMING IS LESSON 1'S POINT AND IT IS THE HIGHEST-VALUE HABIT IN THE MODULE. Name it for what it DOES. A chain called saveCustomer can be found by somebody looking for where customers are saved; one called button2Action can only be found by opening every chain — and a visual tool has no search across everything, which Module 3 Lesson 7 and Module 4 Lesson 10 both said. SIZE IS WHERE THE TWENTY-STEP CHAIN COMES FROM, AND IT IS ALWAYS ARRIVED AT HONESTLY. Validate, call, handle failure, assign, notify — that is five and it is correct. Then a condition, then a second service, then a special…
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