Redwood Adoption Blog Series Part 2: Adopting Redwood – Features, Personalizations, and Page Layout Changes

Welcome to part two of our three-part series exploring the transition to Oracle’s Redwood Experience, presented from the house of MIPRO’s Center of Excellence on Oracle Technologies. This series is designed to help Oracle Cloud customers understand Redwood, what changes during migration, and how to prepare for the shift successfully. Whether you are part of an implementation team, a system administrator, or a business user impacted by the change, these posts provide clarity and actionable insights.

In this post, we explore three high-impact areas to address when migrating to Redwood: new features, personalization behavior, and page layouts. These changes go beyond UI aesthetics — they redefine how the system works for users.

Feature Changes: More Than Cosmetic

What Are Feature Changes? A feature change is a functional improvement that’s exclusive to the Redwood UI in Oracle Cloud. These are not just design updates — they introduce new behaviors or capabilities that improve how the system works. Built using Oracle JET (JavaScript Extension Toolkit), these features are not available in the older Responsive UI.

They often include things like smarter page interactions, improved workflows, or role-based behavior — all made possible by Redwood’s modern framework.

• Smarter page behaviors
• Workflow enhancements
• Dynamic logic based on user roles

Example: Employment Info Page

• Before (Responsive UI): Salary information is visible to all users.
• After (Redwood UI): Role-based logic restricts salary visibility based on access levels.

Business Impact:

• Better control over sensitive data
• Improved compliance with privacy standards
• Reduced exposure to internal data risk

Severity:

Moderate to High – While beneficial, these changes require rethinking how critical data is exposed and governed across roles.

Personalization Changes: A Migration Challenge

What Are Personalizations? Personalizations are UI-level modifications that adjust layout or behavior, such as:

• Making fields required
• Hiding or reordering sections
• Adding embedded content

What Changes with Redwood?

• Personalizations from Responsive UI won’t carry over automatically
• Migration must be handled via:
  • Redwood Personalization Helper Tool
  • Manual updates in Visual Builder Studio

Before (Responsive UI):

• Required fields
• Hidden DFFs
• Embedded OTBI content

After (Redwood):

• Some settings preserved
• Some configurations (e.g., read-only fields) failed to migrate and required manual correction
• All logic needed manual validation in VBS

Impact:

• High — improperly migrated personalizations can disrupt workflows
• Manual testing in each environment (DEV, TEST, PROD) is critical

Page Layout Changes: Understanding Structural Shifts

Redwood introduces redesigned page layouts that may:

• Hide or reposition fields
• Group sections into sub-pages
• Adjust visibility based on default logic

Example: Hire an Employee Page (24A vs. 25A)

• In 24A, 17 toggles were visible (e.g., Family and Emergency Contacts, Weekly Working Hours)
• In 25A, some toggles are hidden or relocated
  • Weekly Working Hours was broken up into new sub-pages

Business Implications:

• Fields required for compliance may be hidden by default
• Administrators must manually re-enable key sections
• Teams must review Redwood’s logic for default page visibility

Severity:

• Moderate – Layout updates can disrupt onboarding, HR transactions, or user expectations if not addressed.

Bringing It All Together

Understanding these core changes — new features, personalization migration, and page layout shifts — is essential to a successful Redwood rollout. While each area poses its own challenges, they also offer significant opportunities for improvement in usability, governance, and efficiency.

As you evaluate your current environment, take time to catalog where legacy configurations exist and identify where Redwood will require a rebuild or revalidation. Teams that proactively plan for these changes will face fewer disruptions and deliver a more seamless user experience.

---

In the final part of this series, we’ll cover the last pieces of the puzzle: Auto-Complete Rules and Security Profiles. We’ll also share a detailed checklist to guide your organization through the final stages of your Redwood transition — from configuration to launch.

If you would like more information on Redwood, visit https://redwood.oracle.com/

Please contact MIPRO for more information on Oracle Cloud. You can also visit Redwood.Oracle.com for additional information.