MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 3 · Pages, flows and navigation

Navigating between pages

Lesson 24 of 176 · 2 min

The mechanisms, and WHAT EACH DOES TO THE BROWSER HISTORY — which is what a user experiences as THE BACK BUTTON WORKING OR NOT. There is more than one way to move a user to another page, and they differ in a way that is invisible while you build and obvious to the person using it. THE DIFFERENCE IS WHETHER THE PREVIOUS PAGE IS PUSHED ONTO THE HISTORY OR REPLACED. Pushed, the back button returns to it. Replaced, the back button skips it entirely and goes wherever the user was before that — which can be outside your application. BOTH ARE CORRECT AND THE CHOICE IS ABOUT WHAT THE STEP MEANT. Moving from a list to a detail is a step forward and should be pushed; the user expects back to return to the list. Redirecting after a successful save is not a step the user took, and pushing it…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 3 · Pages, flows and navigation

  1. 1Flows: the unit that decides your structure
  2. 2Navigating between pages
  3. 3Passing data when you navigate
  4. 4The shell page and what belongs on it
  5. 5Deep links and the URL
  6. 6Layouts, and the page that grew
  7. 7Building for somebody who did not build it
  8. 8Accessibility, from the start
  9. 9What breaks: three navigation failures
  10. 10Lab briefing · Four pages that hang together