Oracle Visual Builder: Applications That Outlive Their First Release · Module 4 · Variables, types and where state lives
Naming state so it is findable
Lesson 42 of 176 · 3 min
A visual tool HAS NO SEARCH ACROSS EVERYTHING. A convention is what stops THE FIFTEENTH VARIABLE BEING A MYSTERY. Module 3 Lesson 7 said this about pages; here it is about state, where it bites hardest, because a variable is the thing you go looking for when something is wrong. THE PROBLEM IS THAT VARIABLES ARE SCATTERED BY DESIGN. Some on this page, some on the flow, some on the application — three places, no combined list, and no way to ask "where is the customer id". You find it by knowing where to look, and knowing where to look is a convention or it is memory. SO THE FIRST THING A NAME SHOULD ENCODE IS WHAT KIND OF THING IT HOLDS. A service result, a user's input, a selection, a flag controlling display. Reading a binding then tells you where the value came from, which is the first question…
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