What is the Redwood Personalization Helper Tool?

It’s a tool provided by Oracle to help you identify and manage personalization/customization changes made in Oracle HCM Responsive Pages (now moving to Redwood UI).

• It generates a report of all personalizations done in HCM Design Studio and some page composer changes.

• It helps you know what personalization is:

  • ✅ Migratable to Redwood

  • ❌ Not supported for migration

💡 What it doesn’t do:

• It does not detect UI text changes (like relabeling fields).

• It’s not mature enough to capture all Page Composer customizations — it focuses more on HCM Design Studio customizations.

✅ Why use this tool?

• To create a summary report of all personalizations done.

• To identify what can be migrated to Redwood and what must be manually rebuilt.

• This is to help you plan during your Redwood migration project.

📄 Reports Generated:

• Excel and HTML reports show:

  • Modules with personalizations (e.g., Pending Worker, Opportunity Marketplace).

  • Type of changes (e.g., required field, hidden field).

  • What is migratable, and what is not?

💡 Flexfield (DFF) Migration:

• If you customized a DFF field (e.g., added a Full-Time/Part-Time field and made it mandatory):

  • You need to check a box in the helper tool to include Flexfields.

  • Provide the target environment URL, username, and password.

  • It will then extract DFF metadata, too.

📦 Migrating Personalizations to Redwood:

Two ways to migrate:

Option 1:

1. Open a Redwood page in the application.

2. Click “Go to Visual Builder Page” → Export workspace (this creates a local branch).

3. In the Helper Tool, select “Migrate & Report” and upload this empty workspace. The tool will generate a new workspace with personalizations.

4. Import this new workspace in Visual Builder Studio and publish it.

Option 2:

• Skip the “export workspace” step and directly use the ZIP file generated from “Migrate & Report” in VBS.

📌 Summary:

• Step 1: Download and install the tool.

• Step 2: Create a working directory.

• Step 3: Export personalizations (Outgoing).

• Step 4: Run report or migrate.

• Step 5: Import results into VBS (if migrating).

• Step 6: Review changes in HTML/Excel reports.

Types of Personalizations It Covers

🔸 Note: UI Text Label changes (like relabeling fields) are not included in any reports.

Report Only Option

Generates a report (Excel/HTML) showing:

You can also filter reports by module (e.g., Time and Labor, Recruiting) to get specific data.

Testing After Migration

• Always verify each migrated page manually in Redwood UI.

• Some changes might appear different due to UI component differences.

• Page Composer personalizations might still need manual review.

Limitations

• No automated migration – it's still semi-manual.

• Not all Page Composer changes are captured.

• No support for UI Text Label relabeling.

• No automatic rollback or reversion capability.

🔧 Why do you need this tool?

When your organization moves from Responsive UI to Redwood UI, some changes/customizations may not carry over automatically.

This tool helps you:

• Check what has been changed

• Understand what can be moved to Redwood

• Create a report and migration files

• Make your transition to Redwood smooth and structured

🧠 Why is this tool necessary?

Oracle is moving from Responsive UI to a new modern interface called Redwood UI.

👉 If you’ve made customizations (like hiding fields, adding fields, making fields required, changing default values, etc.) on your current Responsive pages, you need to know:

• What those customizations are

• Whether they can be moved (migrated) to Redwood

• How to move them easily

That’s where the Redwood Personalization Helper Tool comes in — it acts like a scanner and report generator for your existing personalization.

📘 What does the Redwood Helper Tool actually do?

✔️ It checks:

• What kind of changes you’ve made to your current HCM system

• Which modules or pages those changes were made in

• Whether those changes can be moved to the new Redwood UI or not

✔️ It helps:

• Generate a report (Excel and HTML) showing all personalization

• Create a ZIP file that can be imported into Redwood UI (via Visual Builder Studio)

💡 Example to Understand Better:

📍 You have a page in Oracle HCM like "Add Pending Worker."

You might have done things like:

• Hidden a field

• Made a DFF (Flexfield) required

• Changed the layout

• Changed the default value of a field

🔸 Now, when Oracle moves you to Redwood UI, those changes won’t carry over automatically.

So, this tool helps you identify and carry forward those changes to Redwood using a clean process.

I hope this blog post was helpful for you. If you have any questions or feedback, please leave a comment below.