Oracle Visual Builder: Applications That Outlive Their First Release · Module 4 · Variables, types and where state lives
What breaks: four state failures
Lesson 43 of 176 · 3 min
A VALUE THAT VANISHED ON REFRESH, ONE THAT SURVIVED WHEN IT SHOULD NOT HAVE, A CHANGE LOOP BETWEEN TWO VARIABLES, and A PAGE-SCOPED VALUE FOUR PAGES NEEDED. THE VALUE THAT VANISHED ON REFRESH IS THE ONE USERS MEET FIRST. A form half filled in, an accidental reload, and everything is gone — because every scope dies on refresh and nothing was persisted. Lessons 2 and 7, and the fix is a decision about what may live in a browser rather than a technique. THE ONE THAT SURVIVED WHEN IT SHOULD NOT IS THE MIRROR, AND IT IS QUIETER. An application-scoped value set on one page is still set when the user reaches somewhere unrelated, so a page shows a customer nobody selected or a filter nobody chose. Lesson 3 — the scope was widened for convenience and nothing was made responsible for clearing it. THE CHANGE LOOP IS THE ONE…
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