Oracle Visual Builder: Applications That Outlive Their First Release · Module 3 · Pages, flows and navigation
Building for somebody who did not build it
Lesson 29 of 176 · 3 min
Consistency, labelling, and THE CONVENTIONS THAT LET A SECOND DEVELOPER FIND THE PAGE THEY NEED. Module 1 said the maintenance bill is the whole cost of this product, and this lesson is where that bill is set or avoided. THE PROBLEM IS THAT A VISUAL TOOL HAS NO SEARCH ACROSS EVERYTHING. In code you find things by grepping; here you find things by knowing where they are. So an application somebody else built is navigated by convention or not at all — and if there is no convention, the only way to find the page that shows customer orders is to open pages until one is it. THE FIRST CONVENTION IS THE ONE FROM MODULE 2: NAMES THAT SAY WHAT SOMETHING IS. A flow named for the business area, a page named for the task, a variable named for what it holds. Applied consistently, a stranger can guess where something…
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 3 · Pages, flows and navigation
- 1Flows: the unit that decides your structure
- 2Navigating between pages
- 3Passing data when you navigate
- 4The shell page and what belongs on it
- 5Deep links and the URL
- 6Layouts, and the page that grew
- 7Building for somebody who did not build it
- 8Accessibility, from the start
- 9What breaks: three navigation failures
- 10Lab briefing · Four pages that hang together