Oracle Visual Builder: Applications That Outlive Their First Release · Module 4 · Variables, types and where state lives
State that four pages need
Lesson 41 of 176 · 3 min
The realistic case, and THE THREE WAYS TO SOLVE IT — with THE COSTS OF EACH STATED rather than a recommendation. Four pages need the same value. This is the situation that produces most of the bad state decisions in real applications, and it does not have a right answer — it has three answers with different bills. FIRST: PASS IT. Each page takes it as a parameter and hands it on. The pages stay independent and deep-linkable — Module 3 Lesson 5 — and the cost is that every navigation between them must remember to carry it, so a route somebody adds later arrives without it. Best when the value identifies something, worst when it is large. SECOND: PUT IT IN SHARED SCOPE. One flow variable, all four read it. Simple, nothing to pass, and the cost is that no page works on its own any more — a…
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 4 · Variables, types and where state lives
- 1What a variable is here
- 2The scopes, and what each one meansFree preview
- 3Choosing a scope, deliberately
- 4Types, and why you should declare them
- 5Types that mirror a service
- 6Computed values and expressions
- 7Variables that persist
- 8The event that fires when state changes
- 9State that four pages need
- 10Naming state so it is findable
- 11What breaks: four state failures
- 12Lab briefing · Move state and watch it break