IMPORTANT Actions and Considerations
One-Week Lag Between Readiness Documents Live and Help Center Live
Because Oracle readiness documents (What's New and New Feature Summary) are live one week before the monthly update is applied to Test environments, some links to documentation included in the readiness documents will not work until after the Oracle Help Center update is complete when the monthly update is applied to Test environments.
This update includes Important Actions and Considerations specific to:
- Cloud EPM Platform
- Enterprise Data Management
CLOUD EPM PLATFORM
Cloud EPM Default Idle Session Timeout to be Changed to 30 Minutes
Starting with the November 2025 (25.11) update, Oracle will change the default Cloud EPM idle session timeout to 30 minutes instead of the current 75 minutes. This change enhances session security of Cloud EPM sessions.
Idle Session Timeout is the period after which the user is automatically signed out of the identity domain due to inactivity. If you have a business need to have a longer idle session timeout, Service Administrators can change the timeout value. Shorter Idle Session Timeout value enhances session security.
Cloud EPM to Remove the setIPAllowList and getIPAllowList EPM Automate Commands and the IPAllowList REST API
Starting with the February 2026 (26.02) update, Oracle will remove the setIPAllowList
and getIPAllowList
EPM Automate commands and the IPAllowList
REST API.
These commands and REST APIs were temporary solutions implemented due to the lack of an equivalent security feature in Oracle Identity Cloud.However, with the introduction of Network Perimeter functionality in Oracle Identity Cloud, you can set the allowed and/or blocked IP addresses and CIDRs for the whole domain, which also protects access to Cloud Console.
As part of this transition, the following EPM Automate commands and REST APIS used for managing and viewing IP allowlists are marked as deprecated:
If you use the IP allowlists per environment, you must transition to Network Perimeter by the February 2026 update. See Migrating from Per-Environment IP Allowlist to Network Perimeter in an Identity Domain in the Getting Started Guide for Administrators for detailed information.
Applies to: Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Narrative Reporting, Planning, Profitability and Cost Management, Tax Reporting
Learning Paths Decommissioned
Starting in the December (25.12) update, all Learning Paths will be decommissioned and will no longer be available.
Applies to: Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Narrative Reporting, Planning, Profitability and Cost Management, Tax Reporting
ENTERPRISE DATA MANAGEMENT
Nodes in Viewpoint Loads that Match Top Node Keyword Now Skipped
Starting in this update, if a node in the viewpoint load file has the same name as the Top Node Keyword that you specified in the load options, that record is skipped when the load file is processed.
Improved Property Filtering During Constraint Configuration
Starting in this update, the following criteria is taken into consideration when determining whether a property is available for a particular type of uniqueness constraint:
- For Application Bound or Dimension Bound constraints, a property must be at the Node level, not inherited, and have a Default Type of None only for bound node types in the specified application or dimension.
- For Node Type constraints, a property must be at the Node level, not inherited, and have a Default Type of None only for the node types specified in the constraint (bound or unbound).
JSON Filename Extension Required When Importing and Exporting a Template File
Starting in the December (25.12) update, the filename extension must be JSON only when importing or exporting a template file via the REST API. Specifying a filename extension other than JSON (such as TXT or DAT) will result in a validation error.
Custom Validations Are Now Run on Predefined Members in Cloud EPM Applications
Starting with the August (25.08) update, custom validations are now run on nodes that have the Enterprise Predefined Member property set to True in Enterprise Data Management for Planning Modules, Financial Consolidation and Close, Enterprise Profitability and Cost Management, and Tax Reporting applications. This change in behavior may result in new validation warnings or errors for nodes that did not fail validations in previous releases. Custom validation expressions should be modified to exclude predefined members if the validations should not apply to them.