Oracle Visual Builder: Applications That Outlive Their First Release · Module 8 · Action chains and events
The common actions
Lesson 80 of 176 · 3 min
Calling a service, assigning a variable, navigating, firing a notification. NINETY PER CENT OF EVERY APPLICATION YOU WILL BUILD. The action palette is long and four entries account for almost everything, which is worth knowing before you go looking for something more sophisticated. CALLING A SERVICE IS THE ONE WITH THE MOST AROUND IT. The call itself is one step; what it needs beside it is a loading state, a failure branch and somewhere for the result to go — Lessons 6 and 7, and Module 7 Lesson 8. A service call step with none of those is the commonest incomplete thing in this course. ASSIGNING A VARIABLE IS THE MOST FREQUENT STEP AND THE ONE MOST OFTEN WRITTEN WRONG. Module 7 Lesson 1's rule lives here: assign, do not mutate. An assignment step that writes into an object the variable already holds is the "it did not refresh" defect…
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
