Oracle Redwood UI Migration: Impact on Custom Pages, Analytics, and VBCS Extensions

TL;DR

• Bottom line: Oracle Redwood replaces Classic UI (ADF/Responsive) across all Fusion Cloud modules by 26D/27A — sandbox personalizations do NOT auto-migrate and must be recreated in Visual Builder Studio (VBS).
• Key limit: Classic UI deprecated in 26D (November 2026), decommissioned in 27A (February 2027) — hard deadline.
• Watch out for: Sandbox personalizations are completely lost when a page switches to Redwood — the Helper Tool identifies but does not convert them.
• Best for: Organizations on Fusion Cloud assessing and executing the Redwood transition while preserving customizations.
• Authentication: No auth changes — Redwood is a UI layer change using the same REST APIs and security model.

System Profile

Covers the impact of Oracle’s Redwood Experience transition on Fusion Cloud customizations, extensions, analytics dashboards, and UI-level integration points. Addresses module-by-module timeline, personalization migration, VBCS theme updates, and deep link changes.

API Surfaces & Capabilities

Redwood is a UI/UX transformation — it does not change underlying REST APIs, SOAP services, or integration endpoints.

Rate Limits & Quotas

Redwood Migration Workload Estimates

VBS Sandbox Quotas

Authentication

Redwood does not change the authentication model. All existing auth flows remain unchanged.

Authentication Gotchas

• Deep links with ADF URL parameters may need updating for Redwood format [src4]
• Classic URLs redirect to Redwood but custom integration links may break [src3]
• VBS access requires additional roles (Visual Builder Administrator) [src1]

Constraints

• Sandbox personalizations do NOT auto-migrate to Redwood — must be recreated in VBS
• Not all Classic pages have Redwood equivalents yet — check availability per release
• VBCS Alta theme extensions won’t match Redwood visually — theme migration required
• Custom CSS overrides may break on updates — use stable theme + design tokens
• Cannot opt out once a module’s Redwood pages are delivered
• Helper Tool identifies but does not automatically convert personalizations

Integration Pattern Decision Tree

START — Assessing Redwood UI Impact
├── Customization type?
│   ├── Sandbox Personalizations
│   │   ├── Run Personalization Helper Tool → Get report
│   │   ├── Simple (visibility, layout) → Recreate in VBS (1-2 hours)
│   │   └── Complex (business rules) → Rewrite in VBS+JET (4-8 hours)
│   ├── VBCS Extensions
│   │   ├── Alta theme → Migrate to Redwood theme
│   │   └── Already Redwood → Verify compatibility
│   ├── Custom CSS/Branding
│   │   └── Redesign with stable theme + design tokens
│   └── Embedded Analytics
│       └── Verify rendering in Redwood context
├── Module timeline?
│   ├── HCM → Already mandatory (25C)
│   ├── ERP/SCM → Mandatory (25D-26B)
│   └── CX → Mandatory (26B-26D)
├── Deep links?
│   ├── ADF URLs → Update to Redwood format
│   └── API endpoints → No change
└── Deadline: Classic deprecated 26D, decommissioned 27A

Quick Reference

Redwood Rollout Timeline by Module

Personalization Migration Approach

Step-by-Step Integration Guide

1. Run Redwood Personalization Helper Tool

Generate a comprehensive report of all sandbox personalizations. [src5]

Verify: Report covers all modules with active personalizations.

2. Migrate Personalizations to VBS

Recreate each personalization in Visual Builder Studio using Redwood components. [src1]

Verify: Redwood page shows all personalizations; compare against Classic screenshot.

3. Migrate VBCS Extensions from Alta to Redwood

Update existing VBCS apps to use Redwood theme. [src2]

// Update app-flow.json
// Before: { "theme": "alta" }
// After:  { "theme": "redwood" }
// Replace Alta CSS classes with Redwood design tokens

Verify: VBCS extension visually matches surrounding Redwood pages.

4. Update Deep Links and Integration URLs

Audit and update all external references to Fusion Cloud page URLs. [src3]

Verify: Each deep link preserves user context in Redwood page.

Code Examples

JavaScript: VBCS Theme Migration

// Before (Alta):
function DashboardViewModel() {
  this.buttonClass = ko.observable('oj-button-primary alta-button');
  this.panelClass = 'alta-panel oj-panel-shadow';
}

// After (Redwood — use design tokens):
function DashboardViewModel() {
  this.buttonClass = ko.observable('oj-button-primary');
  this.panelClass = 'oj-panel oj-panel-shadow-sm';
}

CSS: Redwood Stable Theme Override

/* Use stable theme + design tokens — safe across updates */
:root {
  --oj-core-brand-color: #1a73e8;
  --oj-core-brand-color-hover: #1557b0;
}
/* DO NOT reference internal oj-* class names directly */

cURL: Verify REST API Unchanged

# REST APIs are identical before and after Redwood
curl -s "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/workers" \
  -H "Authorization: Bearer $TOKEN" | jq '.count'
# Returns same results regardless of UI mode

Data Mapping

Personalization Type Mapping

Data Type Gotchas

• ADF expression language (EL) has no direct VBS equivalent — rewrite as JavaScript [src1]
• Classic URL parameters may not translate to Redwood format — test deep links [src3]
• OTBI embedding uses different containers in Redwood — verify dimensions [src2]

Error Handling & Failure Points

Common Error Codes

Failure Points in Production

• Personalizations lost after enablement: Fix: Run Helper Tool before enabling Redwood; recreate in VBS first. [src5]
• VBCS visual mismatch: Fix: Migrate VBCS to Redwood theme before enabling on parent module. [src2]
• Custom CSS breaks on update: Fix: Use stable theme base and design tokens only. [src1]
• Email deep links broken: Fix: Update all templates to Redwood URL format. [src3]

Anti-Patterns

Wrong: Assuming personalizations auto-migrate

# BAD — Enable Redwood, expect customizations to appear
# Users log in → custom fields and layouts are GONE
# Classic personalizations do NOT migrate

Correct: Migrate personalizations BEFORE enabling Redwood

# GOOD — 1. Run Helper Tool  2. Recreate in VBS
# 3. Test in Preview  4. THEN enable Redwood

Wrong: Hardcoded CSS class names

/* BAD — Internal class names change between updates */
.oj-navigationlist-item-element { background: #1a73e8 !important; }

Correct: Redwood design tokens

/* GOOD — Design tokens are stable */
:root { --oj-core-brand-color: #1a73e8; }

Wrong: Delaying migration until 26D deadline

# BAD — Only 3 months between 26D deprecation and 27A decommission
# Not enough time for 50+ personalizations

Correct: Phased migration by module

# GOOD — Phase 1: HCM (now) → Phase 2: Procurement/SCM (Q1 2026)
# → Phase 3: Financials (Q2) → Phase 4: CX (Q3-Q4)

Common Pitfalls

• Not running Helper Tool first: Users complain about missing customizations. Fix: Run for every module before enabling Redwood. [src5]
• Mixing Alta and Redwood themes: Jarring visual experience. Fix: Migrate all VBCS extensions before enabling Redwood. [src2]
• Unstable CSS overrides: Break on quarterly updates. Fix: Use design tokens exclusively. [src1]
• Not budgeting for regression testing: Each module needs full testing. Fix: Budget 1-2 weeks per module. [src4]

Diagnostic Commands

# Verify REST APIs unchanged after Redwood
curl -s -o /dev/null -w "%{http_code}" \
  "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/workers" \
  -H "Authorization: Bearer $TOKEN"
# Expected: 200

# Audit deep links in email templates:
# Setup → Manage Notifications → Email Templates
# Search for "fscmUI/faces" (Classic pattern)
# Replace with Redwood URL equivalent

# Check Redwood availability:
# Oracle Cloud Readiness → Module → "Redwood Experience"

Version History & Compatibility

When to Use / When Not to Use

Important Caveats

• Redwood is mandatory — no opt-out after module pages are delivered
• Classic UI decommissioned in 27A (February 2027) — hard deadline
• Helper Tool is useful but incomplete — does not detect all customization types
• Oracle’s timeline has been revised multiple times — track Cloud Readiness
• VBCS on Alta will technically work but creates poor UX with Redwood pages
• Custom CSS must use design tokens — direct class references will break