Oracle Visual Builder: Applications That Outlive Their First Release · Module 6 · Connecting to Fusion
What a service connection is
Lesson 55 of 176 · 3 min
AN ENDPOINT, A SHAPE AND AN AUTHENTICATION METHOD, held once and used everywhere. Why it is A SHARED OBJECT rather than part of a page. A service connection is three facts about somebody else's API, recorded in one place, and the "one place" is what makes it worth a lesson. THE ENDPOINT IS WHERE THE SERVICE LIVES — and it differs between environments, which is the first reason it cannot sit inside a page. Development points at a test pod, production at the real one. Held once, that is one value to change at release; written into pages, it is a search-and-replace nobody completes. THE SHAPE IS WHAT IT RETURNS, AND THE TOOL BUILDS A TYPE FROM IT — Module 4 Lesson 5, with the snapshot warning that lesson gave, and Lesson 8's subject. AND THE AUTHENTICATION METHOD IS WHO YOU ARE WHEN YOU CALL IT, WHICH 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 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