What Is Oracle Redwood? A Complete Guide to Redwood in Oracle Fusion

What Is Oracle Redwood?

Oracle Redwood is Oracle's design system and user experience for Oracle Fusion Cloud Applications. Oracle's guide to extending a Redwood application states that your application is built using Oracle Visual Builder Studio and Oracle JET components, so a Redwood page is a different page technology from the classic ADF interface rather than a restyled version of it.

That distinction is the one that matters for everything below. The rendering framework itself changes, which is why a rebuilt Redwood page is not the old page with new styling on top.

Oracle applies updates to Fusion Cloud Applications four times a year, and its Oracle Cloud Infrastructure documentation states plainly that these updates are mandatory for all customers. In most regions, non-production environments are updated on the weekend following the first Friday of the month, and production on the weekend following the third Friday.

Redwood lands inside that cycle rather than in a single cutover, replacing the classic interface screen by screen.

The Three Things People Mean by "Oracle Redwood"

Most confusion about Redwood comes from one word covering three separate things. Separating them tells you whether the screen in front of you is genuinely rebuilt or simply restyled.

The practical consequence: a team that switched on the Redwood theme has not migrated. Only the third row affects your test suite.

What Is Redwood in Oracle Fusion?

Inside Fusion, Redwood lands as individual pages delivered across quarterly updates. Oracle's Supply Chain and Manufacturing documentation on enabling Redwood pages states that most pages are enabled by using a profile option to turn them on or off, and that at some point, each Redwood page is turned on by default.

That is why Redwood behaves like a rolling program rather than a project with an end date. Each quarterly update can flip another page's default, which changes what your regression suite meets when it next runs.

Customization follows the same split. Classic pages are extended with Application Composer, while Redwood pages are edited in Visual Builder Studio, so personalizations do not automatically carry across when a page is rebuilt.

Redwood UI vs the Classic ADF Interface

The differences that matter to a test engineer are structural rather than visual.

How to Tell Whether a Fusion Page Is Redwood or Classic

Oracle documents a URL rule in its Fusion Applications common documentation: if the third segment contains faces, the page is built using ADF, and if the third segment contains redwood, the page is built using VB Studio.

Reading the URL is therefore faster than inspecting the DOM, and it scales to a whole suite. The operational point is that both kinds of page coexist: your tests are not migrating from one stack to another, they have to straddle both, potentially for years.

Use the rule to inventory your existing regression testing coverage before changing any of it:

• Export the target URL from every test in your Fusion regression suite.
• Bucket each URL by its third segment into ADF, Redwood, or APEX.
• Cross-check the Redwood bucket against the profile options your administrators have already switched on.
• Rank what remains by business criticality, and rework the highest-value flows first.

Which Oracle Products Have Redwood

Oracle publishes Redwood adoption material across its Fusion Cloud Applications families, including ERP, SCM, HCM, Sales, and Service. Maturity differs sharply between them, which is why a blanket statement about "Redwood readiness" is rarely useful.

The question worth answering internally is narrower: for the pillar and release your organization runs, which specific pages have Redwood versions available, and which have already had their defaults flipped. Oracle's per-family release readiness documentation is the source for both, and it changes every quarter.

Enterprise rollouts of this shape rarely stay inside one application, which is why teams running Oracle alongside other business systems usually standardize the approach in a broader enterprise application testing strategy rather than treating each vendor's UI refresh as a separate fire drill.

How to Enable Redwood in Oracle Fusion

Oracle documents the enablement path directly. Its guide to enabling and setting up Redwood pages states that Yes = Enables the feature and No = Disables the feature, and that changes to the profile value affect users the next time they sign in.

How to Disable Redwood in Oracle Fusion

For a page governed by a profile option, reverting is the same procedure with the value set to No. Oracle's enablement documentation defines No as disabling the feature, and the change again takes effect at next sign-in.

To disable a Redwood page in Oracle Fusion:

• Step 1. Confirm the page is reversible. If the feature came from the Opt In page and its Allows Opt-In column is blank, Oracle states it stays always enabled and cannot be turned off.
• Step 2. Open the Setup and Maintenance work area.
• Step 3. Go to Manage Administrator Profile Values.
• Step 4. Search for the profile option code that governs the page.
• Step 5. Set the Site level profile value to No.
• Step 6. Save and close, then have an affected user sign out and back in.

Is Oracle Redwood Mandatory?

You will find confident claims online that all non-Redwood pages stop being supported after a specific release. Checked against Oracle's own readiness documentation, that framing is broader than what Oracle has actually published.

What Oracle has published is a product-scoped end of life, in its End of Life Notice for the Classic Sales and Service Experience: beginning with the 26D update, the Classic interface will enter deprecation status, followed by full removal in the 27A release. That applies to sales and service workflows on the Classic interface, not to Fusion as a whole.

For every other pillar, adoption is enforced gradually instead: Oracle flips individual page defaults over successive quarterly updates. The honest planning answer is that there is no single date to work back from, so the roadmap you should trust is your own pillar's readiness documentation, read every quarter.

Oracle Redwood Roadmap: What Oracle Has Actually Dated

Oracle has not published a suite-wide date after which all of Fusion becomes Redwood. It has published dated commitments for specific products and a fixed update cadence. The table below lists only dates stated in Oracle's own documentation.

Anything you read that gives a single Fusion-wide Redwood deadline is extrapolating from the sales and service notice. Plan against your own pillar's readiness documentation instead, and re-read it each quarter.

What Redwood Changes for Your Existing Test Automation

To check how JET components actually behave rather than reasoning from documentation alone, we ran a live inspection on the public Oracle JET Developer Cookbook using a real Chrome browser on Windows 11 through TestMu AI Browser Cloud. The runtime reported Oracle JET 18.1.0. The findings below come from that session.

// Observed live on Oracle JET 18.1.0 via TestMu AI Browser Cloud.
document.querySelector('#inputSearch|input');
// SyntaxError: Failed to execute 'querySelector' on 'Document':
// '#inputSearch|input' is not a valid selector.

// These three located the same element without error:
document.querySelector('[id="inputSearch|input"]');   // attribute selector
document.querySelector('#' + CSS.escape('inputSearch|input'));
document.getElementById('inputSearch|input');

How to Re-baseline a Fusion Regression Suite for Redwood

Rework the suite in the order that removes risk fastest, rather than rewriting every test at once.

• Inventory tests by URL segment so you know exactly which ones target rebuilt pages.
• Replace CSS id selectors on generated JET ids with By.id, XPath, or an escaped attribute selector.
• Swap element-presence waits for a readiness check on the oj-complete class or the JET busy context.
• Change attribute-reading assertions to property reads so a stale attribute cannot produce a false pass.
• Re-verify personalizations per environment, since logic built in Application Composer does not carry into a rebuilt page automatically.
• Add a visual check on the rebuilt screens, because a layout regression on a redesigned page will not fail a functional assertion.

The last two points are where tooling helps most. KaneAI authors tests from natural-language prompts and re-anchors steps through smart element detection when the UI shifts, which converts a Redwood page rebuild from "rewrite the test" into "review the heal" - the specific failure mode this article has been describing. It exports to Selenium, Playwright, Cypress, and Appium, so adopting it does not strand your existing framework.

For the visual half, SmartUI compares screenshots across browsers and filters rendering noise, which is what makes a redesign diff reviewable instead of a wall of false positives. Teams new to that workflow can start with visual regression testing fundamentals.

Conclusion

Start by exporting the target URLs from your Fusion regression suite and bucketing them by third URL segment. That one pass tells you how much of your suite meets ADF today and how much already meets rebuilt Redwood pages, and it takes an afternoon rather than a planning cycle.

From there, fix the three mechanical issues in order: CSS selectors that cannot parse generated ids, waits that confuse presence with readiness, and assertions that read attributes instead of properties. Those account for most of what breaks, and none of them require waiting for Oracle to announce a deadline that, for most pillars, does not exist.

Because the updates are quarterly and mandatory, the run itself needs to be cheap to repeat. Running that regression on test automation cloud removes the grid maintenance from the equation, and the Selenium 4 documentation covers the setup. If you want the suite to survive the next page rebuild with less rework, the KaneAI documentation is the place to start. For the wider Oracle picture beyond Redwood, our guide to Oracle testing covers update-window strategy and environment planning.