Oracle Cloud 26C Redwood Changes: What’s New?

Oracle Cloud 26C continues Oracle’s push toward Redwood as the standard UX across HCM, SCM, and Financials, expanding Redwood-enabled pages, workspaces, and journeys in employee, manager, and specialist-facing flows. Many Redwood changes are auto enabled, meaning experiences switch over on August 21 without a configuration step, even though they still require impact review, training, and communication. 

Opkey’s 26C Redwood Advisory and Release Advisor turn the full 26C release notes into a focused Redwood impact, testing, and change plan so HR, Payroll, Finance, Procurement, and IT leads can see which Redwood experiences change, assign ownership, and protect operations before the August 21 go-live date. 

Once you know what’s changing, the harder question is how ready your organization is for it. Read our whitepaper to learn more.

Redwood experience: big themes in 26C 

Across the 26C cycle, Redwood continues to move from optional UX to default experience, especially in HCM employment and workflow pages, SCM supply chain work areas, and Financials workbenches and dashboards. Oracle’s release notes call out module-level updates, but the impact is felt in how employees request services, how managers approve and review, and how specialists run operational processes day to day. 

In 26C, Redwood changes include: 

• HCM: Employment, Person, Workforce Structures, Recruiting, Journeys, and Help Desk flows moving to Redwood, with AI-assisted experiences embedded in journeys and key tasks. 

• SCM: Redwood work areas across inventory, orders, supply planning, and manufacturing, with new layouts for key workbenches and exception management. 

• Financials: Redwood dashboards and pages for General Ledger, Payables, Receivables, and Expenses, with updated navigation and task flows. 

These changes alter how users navigate, search, and complete tasks, which is why Opkey’s advisory overlays a Redwood impact lens that highlights which items change UX directly, which sit behind configuration, and which are auto enabled.

Redwood in HCM: employee and manager UX 

In HCM 26C, Redwood is further embedded into core HR and people-facing flows, making it the standard experience for more employment and people management tasks. Redwood-enabled experiences include employment pages, person pages, workforce structures pages, and expanded Redwood journeys, alongside updates to recruiting and talent workflows that use Redwood layouts and components. 

For HR and people leaders, these are not cosmetic changes: they alter how employees submit requests, navigate employment information, and complete onboarding and HR tasks. Opkey’s Redwood advisory flags HCM Redwood items as people-facing, tags them with testing and communication priorities, and surfaces them in “What To Do This Week” action cards so HR owners know which changes need regression testing and which need employee-facing communication before go-live. 

Redwood in SCM: supply chain workspaces 

SCM 26C expands Redwood in operational work areas, so supply chain planners, warehouse teams, and order management specialists increasingly work in Redwood workspaces and dashboards. These changes include new Redwood layouts for planning workbenches, inventory and fulfillment pages, and exception-handling experiences that change how users review, filter, and act on supply chain data. 

Because these experiences are central to day-to-day operations, auto-enabled Redwood transitions can create confusion or productivity dips if teams are not trained ahead of August 21. In Opkey’s advisory, SCM Redwood changes are grouped by work area and severity, so SCM leads can focus on the experiences their users rely on most and align testing and training accordingly. 

Redwood in Financials: workbenches and dashboards 

Financials 26C similarly extends Redwood across finance workbenches and analytic dashboards, with updated page layouts, navigation, and task flows in areas like General Ledger, Payables, Receivables, and Expenses. These updates reshape how finance teams view balances, process transactions, and navigate between related tasks within the same workspace. 

Many of these Redwood changes are designed to streamline tasks, but they still require impact review to confirm that approval flows, reconciliations, and integrations behave as expected in the new UX. Opkey’s advisory tags Financials Redwood items by role (controller, AP/AR, expenses) and enablement type so finance leads can see which changes need regression tests, spot checks, or communication and training. 

Why Redwood 26C is hard to triage manually 

Oracle’s quarterly cadence means customers see Redwood expanding in multiple product families at once, with 26C layering new Redwood experiences on top of already-active ones across HCM, SCM, and Financials. Each Redwood-related change differs whether it is auto-enabled, opt-in, or configuration-dependent, and whether it touches employee-facing UX, operational workspaces, analytics, or integrations. 

When HR, Finance, SCM, and IT teams try to manually sort the 26C release notes to isolate which Redwood changes affect their users, which are auto enabled, and which require setup or service requests, they lose days in a short testing and training window. Without an impact lens, teams risk treating Redwood as “just UI” and missing high-impact changes to journeys, workflows, and workbenches that drive adoption and productivity. 

What Opkey’s 26C Redwood Advisory offers 

Opkey’s Oracle Cloud 26C Redwood Advisory sits between Oracle’s official “What’s New” documentation and internal planning, turning Redwood references in the release notes into a clear impact, ownership, and testing view. In a single dashboard-style PDF organized by role rather than module, it gives HR, Payroll, Finance, SCM, and IT leads: 

• Executive Redwood Snapshot: Key counts of Redwood-enabled pages, workspaces, and journeys across HCM, SCM, and Financials, with a breakdown of auto-enabled versus opt-in experiences. 

• Testing Priority: Redwood changes tagged by High, Medium, and Monitor-only impact so teams can decide which experiences need full regression, which need spot tests, and which need observation post go-live. 

• What To Do This Week by Role: Action cards for HR and Workforce, Finance, SCM, and IT/System Admin, tied to upcoming preview and go-live dates and focused on Redwood UX changes. 

• Impact by Module: Redwood-related change volume and severity across HCM, SCM, and Financials, so each team sees their slice without reading through the entire 26C catalog. 

• Enablement Breakdown: Redwood changes classified by auto-enabled, setup required, potential setup, and opt-in plus service request. 

The advisory is available free at opkey.com and is updated in sync with Oracle’s readiness publications so the Redwood data reflects the current published state of 26C. 

How to use this for 26C Redwood planning 

Start by downloading Opkey’s Oracle Cloud 26C Redwood Advisory and reviewing the Redwood Executive Snapshot with HR, Finance, SCM, and IT leads, focusing first on auto-enabled Redwood transitions in employee-, manager-, and specialist-facing flows. Use the “What To Do This Week by Role” section to assign owners for HCM (HR and Workforce), Financials, SCM, and IT/System Admin, and separately identify which Redwood changes are people-facing and need communication and training plans. 

Then open Opkey Release Advisor at opkey.com/release-advisor and use the prompt guide to explore 26C Redwood changes by product family, module, enablement type, or test level. The Advisor has full context on the 26C catalog and can build a targeted test plan, surface which HCM Redwood changes apply to your employee experiences, which SCM workspaces impact planners and warehouse teams, and which Financials dashboards affect core finance processes, while flagging configuration steps needed by area.