Oracle Visual Builder: Applications That Outlive Their First Release · Module 8 · Action chains and events
What an action chain is
Lesson 78 of 176 · 3 min · Free preview
A NAMED SEQUENCE OF STEPS, TRIGGERED BY SOMETHING. Why it is A FIRST-CLASS THING YOU DESIGN rather than GLUE BETWEEN COMPONENTS. Module 2 named action chains as one of the four things you will live in. This module is about them, and the framing in this title is what decides whether an application stays maintainable. WHAT IT IS: A SEQUENCE OF STEPS, WITH A NAME, THAT SOMETHING STARTS. A button, a page loading, a value changing. The steps run in order, they can branch, and they can call services and set variables. That is the whole of the behaviour layer of every application in this course. THE TEMPTING VIEW IS THAT A CHAIN IS PLUMBING — the wiring that gets a value from a service into a table. Under that view a chain is written per button, named after the button, and never read again. Which is how you arrive…
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 lessonIn 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
