The Planning Quest › What's New
📖 I–III ⚔ IV–V 👑 VI–IX 📘 Gr.I ⚡ Gr.II 📝 Quiz 🃏 Cards 🔬 Labs ⚙ CLI ⚙ Sims 🆕 New 🔍 Search

📡 Oracle EPM Cloud — What's New

Every release tracked · What changed · What it means for your implementation · What you must act on

⚠ 25.11 Production Update Paused — See Notice Below
📢 Critical Notice — December 2025

Oracle paused the 25.11 production update across all EPM environments after identifying issues with Essbase 21.7.x. Updates 25.12 and 26.01 are also paused. Your test environment has 25.11; production remains on 25.10. Fleet updates will resume at 26.02 or later. Submit a Service Request to request early access to 21c patches for critical environments.

Jump to Release
26.01
Jan 2026
Paused
25.11
Nov 2025
Test Only
25.10
Oct 2025
Breaking
25.09
Sep 2025
Depr.
25.08
Aug 2025
Feature
25.07
Jul 2025
Feature
25.06
Jun 2025
Breaking
All
Show all
Breaking change
New feature
Deprecated
Groovy
Data Integration
26.01
January 2026 Update
Paused — SR Required Production: TBD (26.02+)
Security
Role Terminology Change — Predefined → Application Roles + Granular Roles
UI and documentation renames Predefined Roles to Application Roles. Introduces Granular Roles for business-process-specific assignments: Planner, Power User, Viewer are now Granular Roles mapped to Application Roles. This is a terminology and UI change only — underlying permissions are unchanged.
Impact on Quest content: Part VII Lesson 16 (Security) references "Predefined Roles" — will update to 26.01 terminology. No functional change to existing role assignments or security filters. Communicate terminology change to Finance admins to avoid confusion in training materials.
EPM Automate
setIPAllowList / getIPAllowList Commands Fully Removed
Deprecated in 25.09, fully removed from EPM Automate and REST API in 26.01. Any scripts calling these commands will fail with an unrecognised command error. The replacement is Network Perimeter in OCI Identity Domain — configure allowed IP ranges there.
Action Required — Deadline Before 26.02
Search all automation scripts for setIPAllowList and getIPAllowList. Replace with Network Perimeter configuration in OCI Identity Domain admin console → Security → Network Perimeters. Test that service account logins succeed from your automation server IPs after migration.
# Search your scripts for deprecated commands grep -r "setIPAllowList\|getIPAllowList" /your/scripts/directory/ # Replace with: configure Network Perimeter in OCI Identity Domain # No EPM Automate equivalent — management moves to OCI console
Planning
Learning Paths Decommissioned
Oracle's in-product Learning Paths feature is removed in 25.12/26.01. Oracle University courses and external learning resources are unaffected.
Impact: None on implementations. External learning platforms (including The Planning Quest) are unaffected. If you used Learning Paths to onboard new Finance users, replace with a curated Navigation Flow linking to relevant forms and dashboards instead.
Groovy
New Groovy Engine — Stricter Validation Now Live
The new Groovy engine flagged in 25.08 reaches production environments in 26.01 (paused environments: 26.02). Rules using ambiguous method calls, untyped closures, or deprecated Groovy 2.x syntax that previously passed validation may now fail at runtime.
Action Required — Run Diagnostic Before Your Environment Updates
Calculation Manager → Tools → Validate All Groovy Rules. Export the validation report. Common failures: bare def closures passed to typed Java methods, collect/find returning ambiguous types, implicit toString() calls on non-String values. Fix before the engine update reaches your environment.
Impact on Quest content: All Groovy Chapter I and Chapter II examples use explicit typing and typed closures — compliant. Any custom rules following older EPM Community blog patterns (pre-2023 syntax) are higher risk. The BigDecimal pattern, explicit as Integer casts, and typed closure signatures used in this Quest are the correct approach.
25.11
November 2025 Update
Test Env Only Production: Paused (Essbase 21.7.x issue)
Security
Idle Session Timeout Reduced: 75 min → 30 min
Default idle session timeout drops from 75 minutes to 30 minutes across all EPM Cloud environments. Users inactive for 30 consecutive minutes are automatically signed out. Service Administrators can increase this limit in Identity Domain settings (Security → Session Settings → Maximum Idle Time).
Impact on practitioners: Finance users running long FRS jobs, large data exports, or step-by-step form reviews who walk away mid-process will be logged out. EPM Automate service accounts use token-based auth — not affected by session timeout. Review any user-driven processes that exceed 30 minutes and consider breaking them into shorter steps or automating via EPM Automate instead.
If Extended Session Needed
Identity Domain Admin → Settings → Session Settings → Maximum Idle Time. Increase to maximum 8 hours for Finance power users if required. Document the business justification — Oracle security hardening will push timeout lower in future releases.
Security
IP Allowlist Commands Deprecated — Removal in 26.01
setIPAllowList and getIPAllowList EPM Automate commands and the IPAllowList REST endpoint are deprecated in 25.11. Fully removed in 26.01. Migrate all IP restriction management to Network Perimeter in OCI Identity Domain.
Deadline: Before 26.02 Reaches Your Environment
1. Navigate to OCI Identity Domain → Security → Network Perimeters. 2. Create Network Perimeters for each allowed IP range. 3. Assign to the EPM application. 4. Remove setIPAllowList calls from all scripts. 5. Test automation server login succeeds with Network Perimeter active.
Forms
Forms 2.0 — Cell Annotations Now Fully Supported
Cell-level annotations (text notes attached to specific data cells) are now fully supported in Forms 2.0. Previously available in Forms 1.0 with limited styling. Forms 2.0 annotations include: rich text formatting, attachment support, and annotation threading.
FP&A Use Case: Budget reviewers can annotate specific revenue cells with assumption rationale ("Q3 reflects new product launch +$2M"). Finance BP and CFO reviewers can see the rationale without opening a separate Supporting Detail form. Significant reduction in "what's driving this number?" email chains.
Groovy
Groovy Diagnostic Validation Tool — Enhanced Output
The Groovy diagnostic tool (introduced in 25.08) now provides line-level warnings with specific fix recommendations rather than generic "may fail" flags. Output includes the exact Groovy construct flagged, the reason it may fail under the new engine, and the recommended replacement syntax.
Action: Re-run the diagnostic on your test environment (25.11) before production cutover. The enhanced output significantly reduces investigation time — instead of manually reviewing hundreds of lines, you get exact line numbers and fix suggestions.
25.10
October 2025 Update
Breaking Changes Production: Oct 17, 2025
Forms & Dashboards
Forms 1.0 and Dashboard 1.0 — End of Support
All environments now default to Forms 2.0 and Dashboards 2.0. New environments deployed after 25.10 cannot enable Forms 1.0 at all. Existing environments can toggle back to 1.0 temporarily via Application Settings but Forms 1.0 will not receive bug fixes, escalations, or new features from Oracle. The path forward is Forms 2.0 only.
Action Required — Test All Forms Before Cutover
1. Enable Forms 2.0 in test environment: Application Settings → Forms and Dashboards → Forms 2.0 = On. 2. Test all planning forms — pay particular attention to: Apply Context in composite forms, RTP binding, grid suppression rules, action menu positioning. 3. Test all dashboards for 12-component limit compliance. 4. Migrate any classic infolet drill-through actions to Dashboard 2.0 equivalents. 5. Communicate change to Finance users — the grid behaviour for spreading values has subtle differences.
Impact on Quest content: All form design content in Part IV now refers exclusively to Forms 2.0 behaviour. The new Forms 2.0 lesson (Lesson 11) covers Apply Context, the 12-component limit, stateless architecture, and the RTP silent failure pattern in full.
Infolets
Legacy Infolet Actions Removed — Dashboard 2.0 Required
Infolet action configurations supported in Dashboard 1.0 — specifically custom drill-through paths and legacy "Navigate to" actions — are removed in 25.10. Dashboard 2.0 provides replacement capabilities: Analyze (ad-hoc pivot), Open in Smart View, and Spreadsheet Export as context menu items on form grids within dashboards.
Check these specifically: Any infolet where the back face used a custom URL or non-standard action. Reconfigure using Dashboard 2.0 actions or replace with a Navigation Flow shortcut. The new Analyze menu item in Dashboard 2.0 is more powerful than the 1.0 drill-through — it opens full ad-hoc analysis from any form grid in the dashboard.
Smart View
Native Mode Ad Hoc Deprecated — Standard Mode Only
Smart View's "Native mode" for Ad Hoc behaviour is deprecated in 25.10 and will receive no further updates. Standard mode is the only supported mode for escalations and new features. All Smart View ad hoc development going forward must use Standard mode.
Action Required
Application Settings → Smart View Ad Hoc Behaviour → change to Standard. Run a test session with a Finance power user — have them perform their standard ad hoc analysis workflow in Standard mode. Standard mode has improved pivot handling and member selection compared to Native mode in most scenarios.
Groovy
Groovy createFile() — Enhanced File Creation API
The Groovy file creation API (introduced in 25.07 for Excel) is enhanced in 25.10 with CSV and text file creation support. Groovy rules can now create CSV exports and write them directly to the EPM Inbox/Outbox without going through Data Integration.
FP&A Use Case: Generate a budget export CSV from Groovy, format it exactly as your downstream system expects, and place it in the Outbox for EPM Automate to download — all in one scheduled rule. Replaces complex DI export + reformatting pipelines for simple flat-file outputs.
// 25.10: Create CSV from Groovy and send to Outbox def csv = operation.createTextFile() csv.writeLine("Entity,Account,Period,Year,Scenario,Value") entities.each { e -> def val = getCell(e.getName(), "Net_Income", "Full_Year", "FY2026", "Budget", "Working") ?: 0 csv.writeLine("${e.getName()},Net_Income,Full_Year,FY2026,Budget,${val}") } operation.sendFileToOutbox(csv, "budget_export_FY2026.csv")
25.09
September 2025 Update
Deprecations Production: Sep 19, 2025
Data Integration
DI Job Scheduler Migration — Legacy Scheduler Removed
The scheduling UI inside Data Integration (previously Data Management) is removed in 25.09. All job schedules must exist in the EPM Platform Job Scheduler console (Tools → Jobs). The "Migrate Schedules to Platform Jobs Scheduler" automated migration script was also removed — environments that did not migrate during the earlier window must recreate schedules manually.
Action Required — Check Your DI Schedules Now
1. Navigate to Tools → Jobs. 2. Confirm all Data Integration jobs appear here with correct schedules. 3. If missing: in Data Integration, open each integration → Workflow → Schedule → recreate in Platform Jobs. 4. This affects nightly actuals loads, metadata refresh schedules, and rolling forecast automation. A missing schedule = silent failure = Finance arrives to stale data.
Impact on Quest content: Lab 5 (ERP Integration) EPM Automate script uses epmautomate runDataRule directly — unaffected. Any older integrations that relied on DI's internal scheduler must move to either Platform Jobs or external cron/EPM Automate scheduling.
Security
IP Allowlist Commands — First Deprecation Notice
setIPAllowList and getIPAllowList EPM Automate commands first deprecated in 25.09. Will be fully removed in 26.01. Begin migration to Network Perimeter in OCI Identity Domain immediately — the migration window is 3 months.
Who is affected: Any organisation that uses EPM Automate IP restriction features to limit which IP addresses can authenticate to their EPM environment. This is common in high-security financial services and government deployments. If you don't use IP allowlists, no action needed.
Folders
Slash (/) in Folder Names Replaced with Space
Folder names containing the slash character have the slash replaced with a space in 25.09. This resolved a critical backup issue — artifacts stored in slash-named folders were not being included in daily backups. The change is automatic — no admin action required for the rename.
Check immediately: Any EPM Automate scripts, LCM definitions, migration files, or REST API calls that reference folder paths containing "/" need to be updated to use a space instead. Example: a folder path "Reports/Monthly" becomes "Reports Monthly". Search all automation scripts: grep -r "exportSnapshot\|importSnapshot\|copyFile" your_scripts/ and audit folder path arguments.
Narrative Reporting
Report Package Workflow — Author Lock Improvements
Authors in a Narrative Reporting workflow now receive a lock warning when another author has the same doclet open simultaneously. Previously, the second author would silently overwrite the first. The new lock notification shows who has the doclet open and when they last saved.
FP&A Impact: Eliminates the "I just overwrote your commentary" incident that plagued collaborative Board Pack workflows. Particularly valuable in month-end close when multiple Finance BPs are writing commentary simultaneously against the same deadline.
25.08
August 2025 Update
Major Features Production: Aug 15, 2025
Predictive Planning
Advanced Predictions — Multivariate ML Forecasting (EPM Enterprise)
Oracle introduces Advanced Predictions — multivariate machine learning forecasting backed by OCI Data Science. The previous Auto Predict used single-variable (univariate) time series. Advanced Predictions accepts multiple correlated input drivers (e.g. sales volume + average selling price + FX rates + marketing spend) to produce more accurate rolling forecasts. Available across all Planning application types including Freeform. Requires EPM Enterprise Cloud Service subscription. Standard EPM Planning includes the legacy Auto Predict only.
FP&A Impact — Significant: Finance teams that previously relied on moving averages or single-driver extrapolation can incorporate correlated variables without any data science expertise. Oracle's ML model selection is automatic (tries ARIMA, exponential smoothing, regression, and ensemble models; selects the best fit). For Vision Corp's rolling forecast: driver inputs could include order backlog + FX rates + headcount growth → forecast revenue. Expected MAPE improvement: 3–8 percentage points in typical FP&A scenarios vs single-variable Auto Predict.
EPM Automate
Java 8 Discontinued on Linux/UNIX/macOS — Must Use Java 17
EPM Automate on Linux/UNIX/macOS now requires Java 17 minimum. Java 8 runtime is no longer supported. The EPM Automate Windows installer bundles its own Java distribution — Windows users are unaffected. Linux/macOS automation servers must upgrade the Java runtime and update the JAVA_HOME environment variable before the next scheduled run.
Action Required — Linux/macOS EPM Automate Users
Run java -version on every automation server. If not 17+, upgrade immediately. Update JAVA_HOME and PATH. Test EPM Automate login. If using a service account password file (.epw), verify the encrypted file was generated with Java 17 — re-generate if in doubt.
# Verify Java version on automation server java -version # Must show 17.x.x or higher # Update JAVA_HOME (Ubuntu example) export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 export PATH=$JAVA_HOME/bin:$PATH # Add to /etc/profile.d/epmautomate.sh for persistence echo 'export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64' >> /etc/profile.d/epmautomate.sh # Re-test login after Java upgrade epmautomate login [email protected] password.epw https://env.oraclecloud.com
Groovy
New Groovy Engine Announced + Diagnostic Tool Available
Oracle announces a new Groovy engine version with stricter validation rules for H2 2025 / H1 2026. Rules using ambiguous method calls, untyped closures, or deprecated Groovy 2.x syntax patterns may fail under the new engine. Oracle provides a diagnostic program in 25.08 to identify affected rules before the engine switch reaches production.
Action Required — Run Diagnostic on All Environments
Calculation Manager → Tools → Validate All Groovy Rules. This generates a report listing rules that may fail under the new engine. Common issues: (1) bare def closure passed to a typed Java method, (2) ambiguous collect{} return type when chained, (3) BigDecimal arithmetic without explicit rounding, (4) deprecated Groovy 2.x each pattern on Map entries. Run in test first, then production diagnostic (read-only — no rules are changed by the diagnostic).
Impact on Quest content: All Groovy Chapter I and Chapter II examples use explicit typing, BigDecimal with setScale(), typed closures, and safe navigation patterns. These are compliant with the new engine. Rules using bare def throughout without type hints, or old EPM Community patterns from pre-2022 blog posts, are higher risk.
Data Integration
Custom EDM Validations on Predefined Members
From 25.08, custom validation rules in Enterprise Data Management (EDM) now apply to nodes with the Enterprise Predefined Member property set to True. Previously these nodes bypassed custom validations. This may produce new validation errors for predefined members that previously passed cleanly — including Oracle-managed dimension members that your organisation has not touched.
Check in test environment: Run your EDM validation suite against predefined members specifically. If custom validations should NOT apply to predefined members (the most common case), add a condition to each validation expression: [EPM_Predefined] != "Yes". This gates the validation to non-predefined members only.
Data Integration
DI File-Based Integrations — Parallel Processing
File-based Data Integration imports now support parallel processing when multiple source files are available. Previously, multi-file imports processed files sequentially. With parallel processing enabled, DI can process multiple files simultaneously, significantly reducing total load time for implementations that load multiple entity files or multiple data types separately.
Vision Corp use case: SAP extracts a separate file per company code (VISC, VIEU, VIUK, VIAU). Previously these loaded sequentially: 4 × 8 minutes = 32 minutes total. With parallel processing: all 4 load simultaneously = ~10 minutes. Enables tighter nightly windows for multi-entity implementations. Enable in DI → Application Settings → Parallel Processing = On.
25.07
July 2025 Update
New Capabilities Production: Jul 18, 2025
Groovy
Create Excel Workbooks via Groovy + Send to Inbox/Outbox
Groovy rules can now create Excel workbooks programmatically and send them directly to the EPM Inbox/Outbox. Use case: generate a formatted data export, a pre-populated planning template, or a distribution report — all from a scheduled Groovy rule, without manual export steps. The Groovy ExcelWorkbook API wraps Apache POI, supporting multiple sheets, cell formatting, and formulas.
// 25.07: Create Excel workbook from Groovy and send to Outbox def wb = operation.createExcelWorkbook() def sheet = wb.createSheet("Vision_Revenue_Export") def hdr = sheet.createRow(0) hdr.createCell(0).setCellValue("Entity") hdr.createCell(1).setCellValue("Net_Income") hdr.createCell(2).setCellValue("Full_Year") entities.eachWithIndex { e, i -> def row = sheet.createRow(i + 1) def val = getCell(e.getName(), "Net_Income", "Full_Year", "FY2026", "Budget", "Working") ?: 0 row.createCell(0).setCellValue(e.getName()) row.createCell(1).setCellValue(val) } operation.sendFileToOutbox(wb, "Vision_Budget_${year}_${period}.xlsx")
FP&A Use Case: Auto-generate a formatted Board Pack data file as part of the nightly EPM Automate batch. Finance BPs open a current, formatted Excel in their download folder every morning — zero manual export steps. Eliminates the "export → reformat → email" loop that consumed 20–40 minutes of analyst time per reporting cycle.
Groovy
Create ZIP Archives via Groovy
Groovy rules can create ZIP archives containing multiple files and send to Inbox/Outbox. Useful for large data exports that need compression, or for bundling multiple Excel/CSV files into a single delivery package.
Use case: Nightly batch generates 12 entity-level Excel files → ZIPs them → EPM Automate downloads one ZIP → Finance IT extracts and archives. Eliminates 12 individual download calls. Also useful for LCM export bundling in automated deployment pipelines.
Planning
Additional BSO Cubes — Restricted Availability via SR
The ability to create additional Block Storage Cubes beyond the standard Planning plan types (Plan1, Plan2, Plan3) is introduced in 25.07 on a restricted basis. Available only by submitting a Technical Service Request (SR) to Oracle. Not generally available — Oracle is assessing demand and stability before broad release.
When useful: Enterprise implementations needing dedicated BSO cubes for specific planning processes without building a separate application (e.g. a CapEx cube, a custom what-if sandbox cube, a workforce planning extension). Check Oracle's EPM community for current SR template and eligibility criteria.
Data Integration
DI Application Registration Simplification
The application registration flow for source system connections in Data Integration is simplified. Direct connections (Oracle ERP, Oracle HCM) no longer require manual JDBC configuration — Oracle handles the connection string construction from metadata returned by the source system. File-based and non-Oracle sources are unchanged.
Impact on new implementations: Oracle ERP Cloud → EPBCS integration setup time drops from 2–4 hours (manual JDBC, connection testing, troubleshooting) to 30–45 minutes with the guided registration. Existing integrations are not affected — this applies to new registrations only.
25.06
June 2025 Update
Major Breaking Production: Jun 20, 2025
Reporting
Financial Reporting Studio — De-Supported
Oracle Financial Reporting Studio (the legacy FR tool separate from the newer Reports product) is de-supported as of 25.06. All new report development must use Oracle Reports (the modern in-product report builder within Planning). Existing FR Studio reports continue to execute but Oracle will not fix bugs, address escalations, or add features to FR Studio. The migration path is Oracle Reports via the built-in migration tool.
Action Required — Legacy FR Studio Users
1. Audit all reports in Shared Reports → Financial Reports. Identify reports built in FR Studio vs Oracle Reports. 2. Use the Reports Migration tool (Designing with Reports → Appendix B: Migrating Financial Reporting Reports) to convert critical reports. 3. Prioritise: Board Pack reports → close process reports → management reports → ad hoc templates. 4. Document any FR Studio features not available in Oracle Reports — submit an Oracle Enhancement Request for gaps that block migration. A Customer Connect session recording from June 8 covers the migration process in detail.
Impact on Quest content: Part VII covers Oracle Reports (the modern tool) as the primary reporting engine. FR Studio references are now legacy context only. The FRS abbreviation throughout the Quest refers to Financial Reporting Studio (the legacy tool) — new implementations should use Oracle Reports for all new development.
Data Integration
Terminology Standardised — Data Integration Replaces Data Management
Oracle standardises on Data Integration as the official product name across all UI, documentation, APIs, and support references. "Data Management" and "FDMEE" are legacy terminology from pre-cloud EPM. The underlying product capability is identical — only the naming has been formalised. Navigation path changes: Tools → Data Integration (previously Navigator → Data Management in some versions).
Practical impact: Support documentation search is now more reliable — "Data Integration" returns current results; "Data Management" returns a mix of current and legacy. Update your internal runbooks, onboarding guides, and training materials to use "Data Integration" throughout. The Quest uses "Data Integration" exclusively from this release onward.
Planning
Approvals Module Redesigned — New UI and Status API
The Planning Approvals module receives a significant UI redesign in 25.06. The new Approvals interface provides: tree-view hierarchy with status indicators, bulk action support (approve/reject multiple planning units simultaneously), and a new EPM Automate command set for approvals management.
New EPM Automate commands in 25.06:
# New Approvals commands in 25.06 epmautomate listPlanningUnitStatus AppName Scenario Version Year epmautomate promotePlanningUnit AppName Scenario Version Year PlanningUnit epmautomate approvePlanningUnit AppName Scenario Version Year PlanningUnit epmautomate rejectPlanningUnit AppName Scenario Version Year PlanningUnit # Example: check all Vision US entities status epmautomate listPlanningUnitStatus Vision Budget Working FY2026
FP&A Impact: Finance Admin can now monitor the approval status of all 14 department budgets simultaneously from the command line — no need to log into the UI. Automate a daily 7am email showing approval status to the Finance Controller: epmautomate listPlanningUnitStatus Vision Budget Working FY2026 > status.txt && mail -s "Budget Status $(date)" [email protected] < status.txt.
Reporting
Oracle Reports — Grid-Level Database Suppression
Oracle Reports gains grid-level database suppression — rows are suppressed at the Essbase query level rather than post-retrieval. This reduces the data volume returned from Essbase for large reports with many zero rows, eliminating "query result too large" threshold issues that previously required splitting reports into smaller chunks.
Performance impact: Large P&L reports with many zero accounts will load significantly faster — only non-zero rows are returned from Essbase. Enable in Reports → Grid Properties → Database Suppression → On. Vision Corp's Full P&L report (600 account members, 12 entity pages) went from 45-second load to 8 seconds with this setting enabled.
Dashboards
Dashboard 2.0 — Analyze / Smart View / Spreadsheet Export in Context Menu
Dashboard 2.0 form grids gain three new right-click context menu options: Analyze (opens the grid as an ad-hoc analysis pivot), Open in Smart View (opens the data slice in Excel via Smart View), and Spreadsheet Export (exports the current view to Excel). Previously these were only available from standalone forms — dashboard-embedded grids could not be used for ad hoc analysis without navigating away.
FP&A workflow improvement: Finance can go from a dashboard KPI directly to ad-hoc investigation without leaving the dashboard context. Example: CFO notices Revenue is 8% below plan on the dashboard → right-clicks the Revenue cell → Analyze → immediately pivots to see which entity and which product line is driving the variance. The entire workflow stays in the browser — no Smart View launch, no separate form navigation.
Groovy
getRestApiClient() — EPM REST Client Now Scoped to Form Context
The getRestApiClient() method in Groovy form rules is now scoped to the current user's session context, including their security profile. This is the correct way to make REST API calls from Groovy that respect user-level security. The method returns a pre-authenticated client — no manual token management required.
Scope limitations (critical): getRestApiClient() is only available in form rules (beforeSave, afterSave, onLoad) — not in standalone business rules. For business rules that need REST calls, use HttpURLConnection with EPM Automate service account credentials. The Quest's Groovy Chapter II covers this scope distinction in the getRestApiClient() decision tree.
About This Tracker This page covers EPM Cloud Planning releases 25.06 → 26.01. Release notes are sourced from Oracle's official What's New documents and Oracle Cloud Customer Connect. Oracle releases monthly updates on the third Friday of each month (test environments one week earlier). Content is updated within 5 business days of each production release.

Official sources: Oracle EPM Readiness Portal · EPM FAQ