Oracle Visual Builder: Applications That Outlive Their First Release · Module 6 · Connecting to Fusion
What breaks: four connection failures
Lesson 66 of 176 · 3 min
A SHARED ACCOUNT THAT LET EVERY USER SEE EVERYTHING, AN UNPAGINATED LIST, A RENAMED FIELD THAT SILENTLY RETURNED NOTHING, and AN EXPIRED CREDENTIAL. THE SHARED ACCOUNT IS THE MOST SERIOUS AND THE ONE NOBODY DECIDED. A service account chosen because user propagation was not configured yet, never revisited, and an application in which every user has the reach of an integration account. Lessons 3 and 4, and it is invisible from inside because every page filters correctly — the exposure only exists for somebody who calls the endpoint their own page uses. THE UNPAGINATED LIST IS THE ONE THAT WILL DEFINITELY HAPPEN. Built and tested on a handful of rows, correct on that data, and quietly truncating at twenty-five in production. Lesson 6, reported as missing records, and the fix that most people reach for — a very large page size — converts it into a slower version of the…
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 6 · Connecting to Fusion
- 1What a service connection is
- 2Creating one against a Fusion REST APIFree preview
- 3Authentication, and whose identity is used
- 4Why a shared service account is usually wrong
- 5Query parameters, filtering and fields
- 6Pagination, properly
- 7Writing back to Fusion
- 8When the shape changes underneath you
- 9Calling an OIC integration instead
- 10Handling a service that is down
- 11CORS and the errors it produces
- 12What breaks: four connection failures
- 13Lab briefing · Connect, over-fetch, then fix it