MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 6 · Connecting to Fusion

Handling a service that is down

Lesson 64 of 176 · 3 min

What the user sees, what you log, and THE DIFFERENCE BETWEEN AN EMPTY LIST AND A FAILED CALL — which LOOK IDENTICAL IF YOU LET THEM. A service you do not control will be unavailable sometimes. That is not an exceptional case to handle later; it is a state your page will be in, and the default handling of it is the worst possible one. THE DEFAULT IS THAT THE CALL FAILS, THE VARIABLE STAYS EMPTY, AND THE TABLE RENDERS ITS EMPTY STATE. Which reads as "there are no records". That is a factual claim about the business, it is false, and your page is making it confidently on a page a user may act on. THOSE TWO STATES MUST LOOK DIFFERENT AND THE PAGE IS THE ONLY THING THAT CAN MAKE THEM SO. "No orders match this filter" and "We could not reach the order system" lead to completely…

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 6 · Connecting to Fusion

  1. 1What a service connection is
  2. 2Creating one against a Fusion REST APIFree preview
  3. 3Authentication, and whose identity is used
  4. 4Why a shared service account is usually wrong
  5. 5Query parameters, filtering and fields
  6. 6Pagination, properly
  7. 7Writing back to Fusion
  8. 8When the shape changes underneath you
  9. 9Calling an OIC integration instead
  10. 10Handling a service that is down
  11. 11CORS and the errors it produces
  12. 12What breaks: four connection failures
  13. 13Lab briefing · Connect, over-fetch, then fix it