MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 17 · Release readiness: quarterly updates and regression

What is exposed, and what is safe

Lesson 165 of 177 · 2 min

Rank your own artefacts BEFORE testing any of them, because the update window is short and testing everything equally means testing the wrong things thoroughly. MOST EXPOSED: REPORTS. BI Publisher data models read specific tables and views; OTBI analyses read subject areas that gain, lose and rename attributes. Neither is guaranteed the way a service contract is, and a report that quietly returns fewer rows is the worst failure in this course. NEXT: PERSONALISATIONS. Robust where they hide a field, exposed where they depend on a page's structure — and dropped SILENTLY, which is Module 12's Lesson 9. THEN: INTEGRATIONS. Safer than both, because the versioned service contract is the strongest thing Oracle commits to — but a required attribute added to a payload rejects every call, and that is loud rather than silent, which is the right way round. SAFEST: FLEXFIELDS AND APPLICATION COMPOSER EXTENSIONS. Published extension points, carried…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, 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 17 · Release readiness: quarterly updates and regression

  1. 1Reading an update for riskFree preview
  2. 2What is exposed, and what is safe
  3. 3Building a regression pack that stays useful
  4. 4Testing in the update window
  5. 5New features: opting in deliberately
  6. 6Communicating an update to the business
  7. 7What breaks: after the update landed
  8. 8Lab briefing · Assess a real release note