MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 8 · Action chains and events

Chains that call chains

Lesson 82 of 176 · 3 min

Reuse, and THE DEPTH AT WHICH FOLLOWING WHAT HAPPENS BECOMES ARCHAEOLOGY. Where to stop. A chain can call another chain, which is how you avoid writing the same six steps in four places — and it is also how an application becomes impossible to reason about. THE CASE FOR IT IS THE ORDINARY ONE AND IT IS REAL. "Reload the list" is called after a save, after a delete, and after a filter change. Written once, changed once. Written three times, it will differ within a year and nobody will know which version was right. THE CASE AGAINST IS THAT A VISUAL TOOL HAS NO CALL STACK YOU CAN READ. In code, following a call is one click. Here it is opening another artefact, finding your place, and remembering where you came from — and by the third level nobody is holding the whole thing in their head. That is…

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.

See the course and enrol9 free lessons

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 8 · Action chains and events

  1. 1What an action chain isFree preview
  2. 2Events: what can start one
  3. 3The common actions
  4. 4Conditions and branching
  5. 5Chains that call chains
  6. 6Waiting: asynchronous steps
  7. 7Failure inside a chain
  8. 8JavaScript, and when to reach for it
  9. 9Keeping a chain readable
  10. 10Debugging one that misbehaves
  11. 11Logic that does not belong here
  12. 12What breaks: four action chain failures
  13. 13Lab briefing · A chain that survives being read