---
# === IDENTITY ===
id: business/erp-integration/oracle-redwood-ui-impact-integrations/2026
canonical_question: "How does Oracle Redwood UI migration affect custom pages, analytics, and VBCS extensions?"
aliases:
  - "Oracle Redwood UI migration impact on integrations"
  - "Oracle Fusion Redwood customization migration guide"
  - "VBCS Redwood adoption impact on existing extensions"
  - "Oracle Redwood Experience transition effect on custom pages"
entity_type: erp_integration
domain: business > erp-integration > oracle-redwood-ui-impact-integrations
region: global
jurisdiction: global
temporal_scope: 2025-2027

# === SYSTEM PROFILE ===
systems:
  - name: "Oracle Fusion Cloud (Redwood UX)"
    vendor: "Oracle"
    version: "Release 25A-26D"
    edition: "Enterprise"
    deployment: "cloud"
    api_surface: "Visual Builder Studio (VBS), VBCS, REST API"

# === VERIFICATION ===
last_verified: 2026-03-09
confidence: 0.82
version: 1.0
first_published: 2026-03-09

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: volatile
  last_breaking_change: "25A — Redwood mandatory for HCM; 26B target for full coverage; 26D Classic UI deprecated; 27A Classic decommissioned"
  next_review: 2026-09-05
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Classic UI (ADF/Responsive) formally deprecated in 26D (November 2026), decommissioned in 27A (February 2027)"
  - "Sandbox personalizations do NOT auto-migrate to Redwood — must be recreated in VBS"
  - "VBCS extensions built with Alta theme must be migrated to Redwood theme manually"
  - "Redwood Personalization Helper Tool identifies but does not automatically convert all personalizations"
  - "Oracle pushes Redwood by module on a rolling schedule — cannot opt out for modules already switched"
  - "Custom CSS overrides of Redwood theme may break on future updates unless using stable theme"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "Need Oracle EBS to Fusion Cloud migration guidance"
    use_instead: "business/erp-integration/oracle-ebs-to-fusion-migration/2026"
  - condition: "Need Oracle Retail Suite upgrade planning"
    use_instead: "business/erp-integration/oracle-retail-suite-upgrade-planning/2026"
  - condition: "Need Fusion Cloud REST API reference (not UI)"
    use_instead: "Oracle Fusion Cloud REST API documentation"

# === AGENT HINTS ===
inputs_needed:
  - key: current_ui_state
    question: "What is your current UI state?"
    type: choice
    options:
      - "Classic UI (ADF/Responsive) — no Redwood pages yet"
      - "Mixed — some modules on Redwood, others still Classic"
      - "Mostly Redwood — finalizing migration"
  - key: customization_scope
    question: "What types of customizations do you have?"
    type: choice
    options:
      - "Sandbox personalizations only (page layout, field visibility)"
      - "VBCS extensions (custom pages, embedded apps)"
      - "Both sandbox personalizations and VBCS extensions"
      - "Custom CSS themes and branding"
  - key: module_scope
    question: "Which modules are you migrating to Redwood?"
    type: choice
    options:
      - "HCM only"
      - "ERP (Financials, Procurement, SCM)"
      - "CX (Sales, Service)"
      - "Full suite (HCM + ERP + CX)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/erp-integration/oracle-redwood-ui-impact-integrations/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-09)"

# === RELATED UNITS ===
related_kos:
  depends_on: []
  related_to:
    - id: "business/erp-integration/oracle-ebs-to-fusion-migration/2026"
      label: "EBS to Fusion Cloud migration — UI changes during migration"
    - id: "business/erp-integration/oracle-erp-cloud-coexistence-patterns/2026"
      label: "Coexistence patterns — UI considerations during dual-system operation"
  solves: []
  alternative_to: []
  often_confused_with: []

# === SOURCES ===
sources:
  - id: src1
    title: "Oracle VBCS Redwood Adoption"
    author: Apps Associates
    url: https://appsassociates.com/blog/oracle-vbcs-redwood-adoption/
    type: technical_blog
    published: 2024-10-01
    reliability: high
  - id: src2
    title: "Transforming App UI Extensions with Oracle Redwood"
    author: Conneqtion Group
    url: https://conneqtiongroup.com/blog/transforming-app-ui-extensions-with-oracle-redwood
    type: technical_blog
    published: 2024-08-15
    reliability: high
  - id: src3
    title: "Oracle Redwood UI Migration Guide"
    author: MIPRO Consulting
    url: https://miproconsulting.com/oracle-cloud/oracle-redwood/
    type: technical_blog
    published: 2025-01-20
    reliability: high
  - id: src4
    title: "Oracle Fusion to Redwood Migration Guide: Timeline, Strategy, and Best Practices"
    author: USDM
    url: https://usdm.com/resources/blogs/oracle-fusion-to-redwood-migration
    type: technical_blog
    published: 2025-06-01
    reliability: high
  - id: src5
    title: "Redwood Personalization Helper Tool"
    author: Oracle
    url: https://blogs.oracle.com/fusionhcmcoe/redwood-personalization-helper-tool
    type: official_docs
    published: 2024-07-01
    reliability: authoritative
  - id: src6
    title: "Oracle Redwood Transition Summary and Readiness Overview"
    author: Vigilant Technologies
    url: https://vigilant-inc.com/oracle-redwood-transition-summary/
    type: technical_blog
    published: 2025-03-01
    reliability: high
---

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

## TL;DR

- **Bottom line**: Oracle Redwood replaces the Classic UI (ADF/Responsive) across all Fusion Cloud modules by 26D/27A — existing sandbox personalizations do NOT auto-migrate and must be manually recreated in Visual Builder Studio (VBS), while VBCS extensions require theme migration from Alta to Redwood.
- **Key limit**: Classic UI is formally deprecated in update 26D (November 2026) and fully decommissioned in 27A (February 2027) — organizations on Classic UI face a hard deadline.
- **Watch out for**: Sandbox personalizations (page layout changes, field visibility, conditional rendering) made through the traditional sandbox interface are completely lost when a page switches to Redwood — the Personalization Helper Tool helps identify them but does not convert them automatically.
- **Best for**: Organizations running Oracle Fusion Cloud that need to assess, plan, and execute the Redwood UI transition while preserving existing customizations and extensions.
- **Authentication**: No authentication changes — Redwood is a UI layer change that uses the same underlying REST APIs, security model, and role-based access control.

## System Profile

This card covers the impact of Oracle's Redwood Experience transition on existing Oracle Fusion Cloud customizations, extensions, analytics dashboards, and integration points that touch the UI layer. It addresses the migration timeline by module, the fate of existing sandbox personalizations, VBCS extension migration from Alta to Redwood theme, analytics and reporting implications, and strategies for maintaining continuity during the transition. [src4]

| Property | Value |
|---|---|
| **Vendor** | Oracle |
| **System** | Oracle Fusion Cloud Applications (HCM, ERP, SCM, CX) |
| **UI Framework** | Redwood UX (replacing ADF/Responsive Classic UI) |
| **Extension Framework** | Visual Builder Studio (VBS) / VBCS |
| **Current Phase** | Rolling mandatory adoption (25A-26D) |
| **Classic UI Deprecation** | 26D (November 2026) |
| **Classic UI Decommission** | 27A (February 2027) |
| **API Docs** | [Oracle Redwood Design System](https://redwood.oracle.com/) |
| **Status** | Mandatory rollout in progress |

## API Surfaces & Capabilities

Redwood is primarily a UI/UX transformation — it does not change the underlying REST APIs, SOAP services, or integration endpoints. However, it significantly affects the UI extension layer and any integrations that interact with the page surface. [src2]

| Component | Classic UI (Before) | Redwood UI (After) | Integration Impact | Action Required |
|---|---|---|---|---|
| Page Personalizations | Sandbox (ADF Page Composer) | VBS (Visual Builder Studio) | High | Recreate manually in VBS |
| Custom Pages | VBCS with Alta theme | VBCS with Redwood theme | Medium | Theme migration required |
| Embedded Analytics | OTBI/BIP in ADF pages | OTBI/BIP in Redwood pages | Low-Medium | Verify rendering in Redwood |
| Custom Branding/CSS | ADF skin customization | Redwood theme + stable theme override | Medium | Redesign CSS approach |
| Deep Links / URLs | ADF page URLs | Redwood page URLs | Medium | Update bookmarks and integration links |
| REST API Endpoints | Unchanged | Unchanged | None | No action needed |
| SOAP Services | Unchanged | Unchanged | None | No action needed |
| FBDI/ADFdi | Unchanged | Unchanged | None | No action needed |

## Rate Limits & Quotas

### Redwood Migration Workload Estimates

| Activity | Effort Per Item | Notes |
|---|---|---|
| Simple personalization recreation in VBS | 1-2 hours | Field visibility, page layout changes |
| Complex personalization with business rules | 4-8 hours | Conditional rendering, computed fields |
| VBCS extension theme migration (Alta → Redwood) | 2-5 days | Per extension, depending on complexity |
| Custom CSS branding redesign | 1-3 days | Using stable theme override pattern |
| OTBI report verification in Redwood | 1-2 hours | Per report/dashboard |
| Deep link URL updates | 30 minutes | Per link, across bookmarks and integrations |
| Full regression test per module | 1-2 weeks | Per Fusion Cloud module (HCM, ERP, etc.) |

### VBS Sandbox Quotas

| Limit Type | Value | Notes |
|---|---|---|
| Concurrent sandboxes per environment | 5-10 (tenant-dependent) | Shared across all VBS users [src1] |
| VBS extension deployment size | 50 MB (default) | Per application deployment |
| VBS preview instances | 3 concurrent | Per developer sandbox |
| Sandbox lifetime | 90 days default | Auto-expires unless extended |

## Authentication

Redwood does not change the authentication model. All existing authentication flows (SAML 2.0, IDCS, OAuth 2.0) remain unchanged. However, there are implications for user session behavior. [src4]

| Aspect | Classic UI | Redwood UI | Impact |
|---|---|---|---|
| Authentication flow | SAML 2.0 / IDCS | Same | No change |
| Session management | ADF session | JET session | Session timeout behavior may differ |
| Role-based access | Data roles + job roles | Same | No change to security model |
| Deep link authentication | ADF parameter-based | Redwood URL structure | URL format changes may affect SSO redirects |

### Authentication Gotchas

- Deep links that pass authentication context via ADF URL parameters may need updating for Redwood URL structure — test all SSO redirect flows after enabling Redwood on a page [src4]
- Browser bookmarks to Classic UI pages will redirect to Redwood equivalents — but custom integration links that construct URLs programmatically may break [src3]
- VBS sandbox access requires additional roles (Visual Builder Administrator or Application Developer) — users who could personalize via Sandbox may need new roles for VBS [src1]

## Constraints

- Sandbox personalizations made in Classic UI do NOT auto-migrate to Redwood — every personalization must be recreated in VBS [src1, src5]
- Not all Classic UI pages have Redwood equivalents yet — check the Redwood Availability Matrix per module and release [src6]
- VBCS extensions using Alta theme will not visually match Redwood pages — theme migration is required for visual consistency [src2]
- Custom CSS overrides of the Redwood theme may break on future Oracle updates — use the stable theme base to protect against core theme changes [src1]
- Oracle pushes Redwood by module on a rolling quarterly schedule — organizations cannot opt out once a module's Redwood pages are delivered [src4]
- The Redwood Personalization Helper Tool identifies existing personalizations but does not automatically convert them to VBS format — it produces a report that must be manually acted upon [src5]

## Integration Pattern Decision Tree

```
START — Assessing Redwood UI Impact on Integrations
├── What type of customization do you have?
│   ├── Sandbox Personalizations (Page Composer)
│   │   ├── Run Redwood Personalization Helper Tool → Get migration report [src5]
│   │   ├── Simple personalizations (field visibility, layout)?
│   │   │   ├── YES → Recreate in VBS (1-2 hours each)
│   │   │   └── COMPLEX (business rules, computed fields)?
│   │   │       └── Recreate in VBS with Oracle JET components (4-8 hours each)
│   │   └── Personalizations not needed anymore?
│   │       └── Skip — use Redwood defaults (often better)
│   ├── VBCS Extensions (Custom Pages)
│   │   ├── Built with Alta theme?
│   │   │   └── YES → Migrate to Redwood theme
│   │   │       ├── Update CSS → Use Redwood stable theme base
│   │   │       ├── Update components → Replace Alta components with Redwood
│   │   │       └── Test on multiple screen sizes
│   │   └── Built with Redwood theme already?
│   │       └── No action needed — verify compatibility with latest update
│   ├── Custom CSS / Branding
│   │   ├── Using ADF skin?
│   │   │   └── Must redesign → Use Redwood stable theme + CSS overrides
│   │   └── Using custom CSS file?
│   │       └── Review → Some properties renamed or restructured
│   └── Embedded Analytics (OTBI/BIP)
│       ├── Embedded in Classic UI pages?
│       │   └── Verify → Check rendering in Redwood page context
│       └── Standalone dashboards?
│           └── Usually no impact — test anyway
├── Which modules are transitioning?
│   ├── HCM → Already mandatory (25A-25C)
│   ├── ERP/SCM → Mandatory rollout (25D-26B)
│   ├── CX (Sales/Service) → Mandatory (26B-26D)
│   └── Full suite → Phase by module priority
├── Deep links / integration URLs?
│   ├── ADF URLs in external systems?
│   │   └── Update to Redwood URL structure
│   ├── Bookmarks in email templates?
│   │   └── Update — Classic URLs will redirect but may not preserve context
│   └── API endpoints?
│       └── No change — REST/SOAP/FBDI URLs are unchanged
└── Timeline pressure?
    ├── Classic UI deprecated 26D (Nov 2026) → Plan starts now
    └── Classic UI decommissioned 27A (Feb 2027) → Hard deadline
```

## Quick Reference

### Redwood Rollout Timeline by Module

| Module | Redwood Start | Mandatory By | Classic Deprecated | Classic Decommissioned | Priority |
|---|---|---|---|---|---|
| HCM | 24B | 25C (Q3 2025) | 26D | 27A | Highest — already in progress |
| Procurement | 25A | 26A (Q1 2026) | 26D | 27A | High |
| SCM | 25A | 26B (Q2 2026) | 26D | 27A | High |
| Financials (ERP) | 25B | 26B (Q2 2026) | 26D | 27A | High |
| CX (Sales) | 25C | 26D (Q4 2026) | 26D | 27A | Medium |
| CX (Service) | 25C | 26D (Q4 2026) | 26D | 27A | Medium |

### Personalization Migration Approach

| Classic UI Personalization Type | VBS Equivalent | Migration Effort | Helper Tool Coverage |
|---|---|---|---|
| Hide/show fields | VBS page rules | Low (1-2 hours) | Detected |
| Rearrange page layout | VBS page layout editor | Low (1-2 hours) | Detected |
| Add custom fields (EFF) | VBS + EFF setup | Medium (4-8 hours) | Partially detected |
| Conditional field rendering | VBS business rules (Groovy → JET) | High (8-16 hours) | Detected but not converted |
| Custom page sections | VBS page fragments | Medium (4-8 hours) | Not detected |
| Custom actions/buttons | VBS + REST API integration | High (1-2 days) | Not detected |
| Embedded OTBI dashboards | VBS embedding + verification | Low (2-4 hours) | Not detected |

## Step-by-Step Integration Guide

### 1. Run Redwood Personalization Helper Tool

Use Oracle's Helper Tool to generate a comprehensive report of all existing sandbox personalizations that need migration. [src5]

```
# Access the Redwood Personalization Helper Tool:
# 1. Navigate to: Setup and Maintenance → Manage Sandboxes
# 2. Open the Personalization Helper Tool (available from 24B+)
# 3. Select modules to scan (HCM, ERP, SCM, CX)
# 4. Run scan — generates CSV/PDF report listing:
#    - Page name
#    - Personalization type (layout, visibility, conditional)
#    - Complexity rating (simple/moderate/complex)
#    - Compatible with Redwood auto-migration? (Yes/No)
# 5. Download report for migration planning
```

**Verify**: Report covers all modules with active personalizations — compare count against known customization inventory.

### 2. Migrate Sandbox Personalizations to VBS

For each personalization identified by the Helper Tool, recreate it in Visual Builder Studio using Redwood components. [src1, src5]

```
# VBS Personalization Migration Process:
# 1. Open Visual Builder Studio → Application Extensions
# 2. Create a new sandbox for migration work
# 3. Navigate to the Redwood page equivalent of the Classic page
# 4. Use Page Designer to apply equivalent personalizations:
#    - Field visibility → Use "Visible" property with condition
#    - Layout changes → Drag-and-drop in Page Designer
#    - Business rules → Create Rule in VBS (replaces Groovy)
# 5. Test in VBS Preview mode on desktop and mobile
# 6. Publish sandbox → Test in non-production environment
# 7. Promote to production via Change Management
```

**Verify**: Open the Redwood page — verify all personalizations are visible and functional. Compare screenshot against Classic UI version.

### 3. Migrate VBCS Extensions from Alta to Redwood Theme

Update existing VBCS custom applications to use the Redwood design system instead of Alta. [src2]

```javascript
// Step 1: Update app-flow.json to use Redwood theme
// Before (Alta):
{
  "theme": "alta",
  "requirejs": { "paths": { "ojs": "libs/oracle/jet" } }
}

// After (Redwood):
{
  "theme": "redwood",
  "requirejs": { "paths": { "ojs": "libs/oracle/jet" } }
}

// Step 2: Update component references
// Replace Alta-specific components with Redwood equivalents:
// - oj-button (Alta) → oj-button (Redwood — same component, different styling)
// - Custom CSS classes → Use Redwood design tokens
// - Alta color variables → Redwood color tokens

// Step 3: Create stable theme override for custom branding
// In web app settings → Redwood theme → Create CSS override file
// Use stable theme base to protect against Oracle's future theme changes
```

**Verify**: Preview VBCS extension in Redwood mode — verify visual consistency with Redwood Fusion pages on desktop and mobile.

### 4. Update Deep Links and Integration URLs

Identify and update all external references to Fusion Cloud page URLs that may change with Redwood. [src3]

```bash
# Audit deep links in external systems:
# 1. Search email templates for ADF URLs:
#    Pattern: https://<pod>.fa.us2.oraclecloud.com/fscmUI/faces/...
# 2. Search integration flows (OIC) for UI-level URLs
# 3. Search documentation/wikis for bookmarked Fusion pages
# 4. Search SSO/SAML configurations for redirect URLs
#
# Redwood URL format:
#    https://<pod>.fa.us2.oraclecloud.com/fscmUI/redwood/...
# Classic redirect behavior:
#    Classic URLs redirect to Redwood equivalents
#    BUT: URL parameters may not be preserved
#    TEST each deep link after Redwood enablement
```

**Verify**: Each deep link resolves correctly and preserves user context (record ID, parameters) in the Redwood page.

## Code Examples

### JavaScript: VBCS Extension Theme Migration

```javascript
// Input:  Existing VBCS extension with Alta theme
// Output: Updated extension with Redwood theme

// Example: Migrating a custom dashboard component
// Before (Alta theme):
define(['ojs/ojcore', 'knockout', 'ojs/ojbutton'],
  function(oj, ko) {
    function DashboardViewModel() {
      this.buttonClass = ko.observable('oj-button-primary alta-button');
      // Alta-specific styling
      this.panelClass = 'alta-panel oj-panel-shadow';
    }
    return DashboardViewModel;
  });

// After (Redwood theme):
define(['ojs/ojcore', 'knockout', 'ojs/ojbutton'],
  function(oj, ko) {
    function DashboardViewModel() {
      // Redwood uses design tokens instead of Alta classes
      this.buttonClass = ko.observable('oj-button-primary');
      // Redwood panel styling — use design tokens
      this.panelClass = 'oj-panel oj-panel-shadow-sm';
    }
    return DashboardViewModel;
  });
```

### CSS: Redwood Stable Theme Override

```css
/* Input:  Custom branding requirements (logo, colors)
   Output: Safe CSS override using Redwood stable theme */

/* IMPORTANT: Use stable theme to protect against Oracle updates.
   In VBCS: Web App Settings → Redwood theme → Create link → Stable theme
   Then override in this CSS file */

/* Safe overrides using Redwood design tokens */
:root {
  /* Brand colors — override Redwood defaults */
  --oj-core-brand-color: #1a73e8;
  --oj-core-brand-color-hover: #1557b0;
  --oj-header-bg-color: #ffffff;
  --oj-header-border-color: #e0e0e0;
}

/* Custom header branding */
.oj-web-applayout-header {
  background-color: var(--oj-header-bg-color);
  border-bottom: 2px solid var(--oj-core-brand-color);
}

/* DO NOT override these — they change between Redwood updates:
   - Internal component class names (oj-*)
   - Layout grid measurements
   - Font sizes (use design tokens instead)
*/
```

### cURL: Verify REST API Unchanged After Redwood

```bash
# Input:  Fusion Cloud credentials, existing REST API endpoints
# Output: Confirmation that REST APIs work identically after Redwood

# Redwood does NOT change REST API endpoints
# This test confirms API-level integrations are unaffected:

TOKEN=$(curl -s -X POST "https://<idcs-url>/oauth2/v1/token" \
  -d "grant_type=client_credentials&scope=urn:opc:resource:consumer::all" \
  -u "<client_id>:<client_secret>" | jq -r '.access_token')

# Test same endpoint before and after Redwood enablement
curl -s "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/workers" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" | jq '.count'
# Should return identical results regardless of UI mode
```

## Data Mapping

### Personalization Type Mapping: Classic to Redwood

| Classic UI Component | Redwood VBS Equivalent | Migration Approach | Notes |
|---|---|---|---|
| Page Composer → Hide Field | VBS Rule → Set Visible=false | Manual in VBS Page Designer | Condition logic must be recreated |
| Page Composer → Rearrange Layout | VBS Page Layout Editor | Manual drag-and-drop | Redwood layout grid differs from ADF |
| Groovy Script (conditional) | VBS Business Rule (JavaScript) | Rewrite logic | Groovy syntax differs from JavaScript |
| ADF Task Flow customization | VBS Application Extension | Significant redesign | Architecture is fundamentally different |
| Oracle BI Publisher embed | VBS Component + BIP iframe | Minor adjustment | Verify iframe rendering in Redwood |
| ADF custom skin CSS | Redwood stable theme + CSS override | Redesign | CSS properties and selectors changed |

### Data Type Gotchas

- ADF expression language (EL) used in Classic personalizations has no direct equivalent in VBS — business rules must be rewritten in JavaScript [src1]
- Classic UI page parameters passed via URL (faces/...) may not translate to Redwood URL format — test deep links explicitly [src3]
- OTBI report embedding uses different container components in Redwood — verify report rendering dimensions and interactivity [src2]

## Error Handling & Failure Points

### Common Error Codes

| Code | Context | Meaning | Cause | Resolution |
|---|---|---|---|---|
| VBS-SANDBOX-001 | VBS | Sandbox creation failed | Max concurrent sandboxes reached | Close unused sandboxes; wait for expiry |
| VBS-DEPLOY-403 | VBS | Deployment forbidden | Missing Visual Builder Administrator role | Grant role to user in Security Console |
| REDWOOD-PAGE-404 | UI | Redwood page not available | Page not yet converted to Redwood in current release | Stay on Classic for this page until next release |
| CSS-OVERRIDE-BROKEN | UI | Custom styling lost after update | Used unstable Redwood theme class names | Switch to stable theme base; use design tokens |
| DEEP-LINK-REDIRECT | Integration | URL redirect loses parameters | Classic URL format not fully compatible | Update URL to Redwood format |

### Failure Points in Production

- **Personalizations lost after Redwood enablement**: Users report missing fields and layout changes when a page switches to Redwood. Fix: `Run Personalization Helper Tool before enabling Redwood on any page; recreate all personalizations in VBS first`. [src5]
- **VBCS extension visual mismatch**: Custom VBCS pages still show Alta styling while surrounding Fusion pages show Redwood. Fix: `Migrate VBCS extensions to Redwood theme before enabling Redwood on the containing module`. [src2]
- **Custom CSS breaks on quarterly update**: Oracle updates Redwood theme internals, breaking custom CSS that relied on internal class names. Fix: `Use stable theme base and Redwood design tokens only; never reference internal oj-* class names directly`. [src1]
- **Email template deep links stop working**: Hardcoded Classic UI URLs in notification templates redirect but lose record context. Fix: `Update all email/notification templates to use Redwood URL format; test each template after Redwood enablement`. [src3]

## Anti-Patterns

### Wrong: Assuming personalizations auto-migrate to Redwood

```
# BAD — Enabling Redwood on a module and expecting personalizations to appear
# 1. Enable Redwood on Financials pages
# 2. Users log in → custom fields and layouts are GONE
# 3. Users report "my customizations disappeared"
# This is by design — Classic personalizations do NOT migrate
```

### Correct: Migrate personalizations BEFORE enabling Redwood

```
# GOOD — Migration-first approach:
# 1. Run Personalization Helper Tool → Get report of all customizations
# 2. Recreate each personalization in VBS sandbox
# 3. Test in VBS Preview mode
# 4. Publish VBS sandbox
# 5. THEN enable Redwood on the module pages
# 6. Users see customizations + Redwood UI simultaneously
```

### Wrong: Overriding Redwood CSS with hardcoded class names

```css
/* BAD — These internal class names change between Oracle updates */
.oj-navigationlist-item-element {
  background-color: #1a73e8 !important; /* Will break */
}
.oj-flex-bar-end .oj-button-text {
  color: white !important; /* Will break */
}
```

### Correct: Use Redwood design tokens and stable theme

```css
/* GOOD — Design tokens are stable across updates */
:root {
  --oj-core-brand-color: #1a73e8;
}
.oj-web-applayout-header {
  background-color: var(--oj-header-bg-color);
}
/* Use stable theme base — Oracle commits to backward compatibility */
```

### Wrong: Delaying Redwood migration until the deadline

```
# BAD — Waiting until 26D (November 2026) to start migration
# Classic UI deprecated in 26D, decommissioned in 27A (February 2027)
# That's only ~3 months to migrate ALL personalizations + extensions
# Organizations with 50+ personalizations cannot finish in time
```

### Correct: Start phased migration aligned with module rollout

```
# GOOD — Phase migration by module priority
# Phase 1 (NOW): HCM — already mandatory
# Phase 2 (Q1 2026): Procurement + SCM
# Phase 3 (Q2 2026): Financials
# Phase 4 (Q3-Q4 2026): CX modules
# Each phase: inventory → migrate personalizations → test → enable
```

## Common Pitfalls

- **Not running the Personalization Helper Tool first**: Organizations enable Redwood without knowing what personalizations exist, then face user complaints about missing customizations. Fix: `Run the Helper Tool for every module before enabling Redwood; export the report as your migration checklist`. [src5]
- **Mixing Alta and Redwood themes in VBCS**: Some VBCS pages use Alta while Redwood is enabled on surrounding Fusion pages, creating a jarring visual experience. Fix: `Migrate all VBCS extensions to Redwood theme before enabling Redwood on the parent module`. [src2]
- **Using unstable CSS overrides**: Custom CSS that references Oracle's internal class names breaks on quarterly updates. Fix: `Use Redwood design tokens exclusively; switch to stable theme base for any CSS overrides`. [src1]
- **Ignoring deep link updates**: Email templates, bookmarks, and integration links that construct Classic UI URLs stop working correctly. Fix: `Audit all deep links across email templates, notification configs, OIC flows, and documentation; update to Redwood URL format`. [src3]
- **Not budgeting for regression testing**: Each module's Redwood migration requires full regression testing of all personalizations, extensions, and analytics. Fix: `Budget 1-2 weeks per module for regression testing; automate tests where possible using Selenium or similar`. [src4]

## Diagnostic Commands

```bash
# REST APIs are unchanged — verify they still work 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 (same before and after Redwood)

# Check which Fusion Cloud release you are on
curl -s "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/" \
  -H "Authorization: Bearer $TOKEN" | jq '.items[0]'

# Verify VBS sandbox status (via Fusion UI):
# Setup and Maintenance → Manage Sandboxes
# Check: active sandboxes, their owners, and expiry dates

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

# Check Redwood page availability for your release:
# Oracle Cloud Readiness → Module → Look for "Redwood Experience" features
# URL: https://cloud.oracle.com/cloud-readiness
```

## Version History & Compatibility

| Release | Date | Redwood Changes | Impact |
|---|---|---|---|
| 27A | 2027-02 | Classic UI fully decommissioned | Hard deadline — Classic pages removed |
| 26D | 2026-11 | Classic UI formally deprecated | No new Classic features; deprecation warnings |
| 26B | 2026-05 | Target for full Redwood coverage | All modules should have Redwood pages |
| 25D | 2025-11 | ERP/SCM Redwood mandatory | Financials, Procurement, SCM forced to Redwood |
| 25C | 2025-08 | HCM Redwood mandatory, CX starts | HCM complete; Sales/Service begin |
| 25A | 2025-02 | Redwood rollout begins (HCM, Procurement) | First mandatory modules |
| 24B | 2024-05 | Redwood pages available (opt-in) | Optional enablement for early adopters |

### Deprecation Policy

Oracle has committed to the Redwood transition with a firm timeline. Classic UI (ADF/Responsive) is deprecated in 26D and decommissioned in 27A. Oracle will not extend Classic UI support beyond 27A. All sandbox personalizations must be migrated to VBS before 27A. VBCS extensions on Alta theme will still function but will appear visually inconsistent with Redwood pages. [src4, src6]

## When to Use / When Not to Use

| Use When | Don't Use When | Use Instead |
|---|---|---|
| Assessing Redwood impact on existing customizations | Need EBS to Fusion Cloud migration guidance | oracle-ebs-to-fusion-migration/2026 |
| Planning VBCS extension migration from Alta to Redwood | Need REST API technical reference | Oracle Fusion Cloud REST API docs |
| Migrating sandbox personalizations to VBS | Need Oracle Retail Suite upgrade planning | oracle-retail-suite-upgrade-planning/2026 |
| Understanding Redwood timeline and hard deadlines | Need integration middleware guidance | Oracle Integration Cloud documentation |

## Important Caveats

- Redwood is a mandatory transition — there is no "opt-out" option after a module's Redwood pages are delivered
- Classic UI is decommissioned in 27A (February 2027) — this is a hard deadline, not a soft suggestion
- The Personalization Helper Tool is useful but incomplete — it does not detect custom page sections, embedded analytics, or VBCS extensions
- Oracle's Redwood timeline has been revised multiple times — track Oracle Cloud Readiness for the latest dates
- VBCS extensions on Alta theme will technically still work after Redwood enablement but will create a poor user experience due to visual inconsistency
- Custom CSS overrides must use Redwood design tokens and stable theme base — any direct class name references will break on future updates

## Related Units

- [Oracle EBS to Fusion Cloud Migration](/business/erp-integration/oracle-ebs-to-fusion-migration/2026) — UI changes are part of the broader EBS migration picture
- [Oracle ERP Cloud Coexistence Patterns](/business/erp-integration/oracle-erp-cloud-coexistence-patterns/2026) — UI considerations during dual-system coexistence
- [Oracle Retail Suite Upgrade Planning](/business/erp-integration/oracle-retail-suite-upgrade-planning/2026) — Retail admin interfaces affected by Redwood