Oracle's Redwood UI is the new standard for Fusion HCM. If your organization is still on the classic UI, migration is inevitable. Here is the practical checklist I used — tested against a real implementation.
Phase 1 — Audit Your Current Configuration
- List every custom page layout and flexfield configuration
- Identify personalizations that will not carry over automatically
- Document all custom BIP reports that display within HCM pages
- Note any third-party integrations that depend on classic UI URLs
Phase 2 — Enable Redwood in Sandbox
Navigate to Setup and Maintenance → Manage Administrator Profile Values. Search for the profile option HCM_EXPERIENCE_DESIGN_MODE and set it to REDWOOD at the Site level — in Sandbox only first.
✦ Never enable Redwood in Production before completing a full regression test in Sandbox. Some workflows behave differently, especially absence and performance forms.
Phase 3 — Test High-Traffic Pages First
| Page | Test Focus | Risk Level |
|---|---|---|
| My Team → Absence | Absence request flow end-to-end | High |
| Performance → Goal Setting | Goal creation and approval chain | High |
| Payslip view | Rendering and download | Medium |
| Learning → My Courses | Course launch and completion | Medium |
| Directory search | Search results and person card | Low |
Phase 4 — Promote to Production
After sign-off in Sandbox: enable Redwood at Site level in Production during a low-traffic window. Prepare a rollback plan — you can revert the profile option if critical issues arise.
The Biggest Lesson
The technical switch takes minutes. The people side takes weeks. Invest in quick reference cards and short demo videos for end users — these reduce helpdesk tickets by more than any technical preparation.
No comments:
Post a Comment
Thanks for your comments submitted.,will review and Post soon! by admin.