Oracle Integration Cloud: Building Integrations That Survive Production · Module 6 · Orchestration patterns
Local variables and assignment
Lesson 63 of 175 · 2 min
Holding state across steps WITHOUT abusing the payload as a scratchpad. A local variable is declared, assigned, and read by later steps. That is the whole mechanism, and the discipline is entirely about what you put in one and what you call it. WHAT VARIABLES ARE FOR: a counter, an accumulated list of failures, a flag set by one branch and read by another, a value looked up once and used three times. Anything a later step needs that is not simply the previous step's response. WHAT ABUSING THE PAYLOAD LOOKS LIKE: adding fields to the message as it moves through the flow, so that by step eight the structure carries a mixture of what arrived, what was looked up, and what somebody needed to remember. It works, and it makes the flow unreadable — because nobody can tell which parts of the structure are the message and which are…
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.
In this module: Module 6 · Orchestration patterns
- 1App-driven versus scheduled
- 2Invokes, and the shape of a flow
- 3Switch, and branching honestly
- 4Loops over collections
- 5Local variables and assignment
- 6Sub-integrations and reuse
- 7Synchronous versus asynchronous
- 8Stitching in a database or file step
- 9When an orchestration is too big
- 10What breaks: three orchestration failures
- 11Lab briefing · Build a four-step flow