Monthly updates, on Oracle's calendar

EPM Cloud updates every month whether you like it or not. The teams that never get surprised follow one small routine. This page is that routine, and the 2026 evidence for why.

RuleRead the What's New before the test update lands, exercise the test pod in the window before production, and hold a fresh snapshot going in.

Neverbuild on interface behavior. Screens are the one layer Oracle changes without asking; jobs and APIs are the layers that hold.

◆ The cadence, and the window that is yours— test first, production later, and what to do in between.

Beat	What happens
Monthly, test first	The update reaches test environments ahead of production in the same month. That gap is your testing window, it exists for exactly this.
In the window	Run the close in miniature: your integrations, your key forms, your scripts, one pass each. Fifteen minutes of routine beats a Monday of surprise.
Before production	A snapshot from the night before the production update is your rollback evidence and your audit answer, one exportSnapshot in the nightly script covers it.
If you must delay	Skipping an update exists but requires a service request, and you only defer, never avoid. Use it for a badly timed close, not as a habit.

◆ What 2026 proved— five real changes, one year, each a reason the routine exists.

Change	The lesson
The Essbase 21c wave	The engine under every cube changed, calculation accuracy issues surfaced, and Oracle paused production updates while it settled. Environments with a testing routine caught differences in the window; the rest found them in the close.
Stricter Groovy engine, May 2026	Rules that ran for years failed the new validation, and server-side rules now require HTTPS. Oracle shipped a validator ahead of time; the routine is what makes you run it.
EPM Automate moved, April 2026	New install path, password files must sit in the ProgramData folder, and failed calls stopped retrying on permission errors. Working scripts broke for teams that never read the notes.
Forms 1.0 and Dashboards 1.0 desupported	Old interface layers get switched off on schedule. Anything built on them inherits the deadline.
New features gated to current updates	The 2026 AI capabilities require the April update or later. Staying current is also how you stay eligible.

The routine is four habits: read the notes, test in the window, snapshot before production, and build on jobs and APIs, the layers built exactly so that the monthly calendar cannot touch your pipeline. Everything on this page is drawn from Oracle's update documentation and the 2026 update record, verified July 2026.

Want the update routine installed and owned?

The checklist, the test-window script, the snapshot in the nightly job, and a pipeline the monthly calendar cannot break.

Talk to us

Terms on this page

What's New: Oracle's monthly update notes. The routine starts here.
the window: The gap between the test update and production. Yours, use it.
skip request: The service request that defers one update. A tool for a badly timed close, not a habit.
desupport: A feature's scheduled end. Anything built on it inherits the date.