MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse

Editing a lookup safely

Lesson 111 of 175 · 2 min

LOOKUPS ARE LIVE: A CHANGE TAKES EFFECT ON THE NEXT RUN WITH NO ACTIVATION AND NO VERSION. The consequence, and the discipline that follows from it. That is the whole point of a lookup and it is also the entire risk. Everything else in OIC is versioned and activated — you edit a draft, you activate it, and the change is a deliberate act with a record. A lookup has none of that. Save it and the next instance uses the new value. SO A MISTYPED ROW IS A PRODUCTION CHANGE, IMMEDIATELY, MADE BY WHOEVER HAD THE CONSOLE OPEN. There is no draft, no version to compare against, no rollback, and — this is the part people do not expect — no record of what the value was before. The row simply reads differently now. THE DISCIPLINE THAT FOLLOWS IS THREE THINGS, and none of them is technical. EXPORT BEFORE

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.

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 11 · Lookups, libraries and reuse

  1. 1Lookups: the cross-reference table
  2. 2Editing a lookup safely
  3. 3JavaScript libraries in OIC
  4. 4Reusable connections and naming
  5. 5Configuration versus hard-coding
  6. 6What breaks: the lookup nobody owned
  7. 7Lab briefing · Externalise the hard-coded values