Enterprise-Ready Redwood customisation is more than just a design system—it’s the new digital experience layer for Fusion Applications, offering a unified, responsive, and visually consistent interface across HCM, Finance, SCM, and other modules. To take full advantage of Redwood, enterprises often rely on Oracle Visual Builder Studio (VBS) to design, extend, and roll out Redwood-based customisations in a secure, upgrade-friendly manner. 

This guide outlines how to establish an Enterprise-Ready Redwood customisation for an operating model with VBS—covering version control, branching, pipelines, team collaboration, and governance.

Why Redesign Using VBS? 

Aspect	Red Hat	Why VBS Matters
UX Framework	Redwood standardises look and feel across HCM, Finance, SCM, etc.	Ensures consistency, accessibility, and future alignment
Customisation Environment	Visual Builder gives a sandboxed, version-controlled environment	Enables safe, upgrade-safe customisations without altering core code
DevOps Integration	VBS integrates with Git, CI/CD pipelines, approvals, and audit logs	Supports collaboration, rollback, and automation

Key Components of the VBS Workflow 

1. Projects 

• Group customisations into logical domains (e.g., HCM_Redwood_Customisations). 
• Each project manages repositories, workspaces, and pipelines. 

2. Repositories & Branching 

• Use Git best practices. 
• Keep main or release branches stable. 
• Create feature branches for enhancements (feature/hr-pages, feature/payroll-ui). 

3. Workspaces 

• Developers work in isolated sandboxes. 
• Workspaces can be organised by module (HCM, Payroll, Recruiting) or developer. 

Take your expertise to the next level with our
Visual Builder Cloud Service (VBCS) Training

4. Express vs. Advanced Mode 

• Express Mode: Ideal when you need quick, no-code adjustments, including conditional display, simple validation, and default settings. 
• Advanced Mode: For complex scenarios—REST calls, event handling, action chains. 

5. Pipelines & Jobs 

• Automate builds, validations, and deployments. 
• Insert approval checkpoints for enterprise compliance. 
• Enable rollback for failed builds. 

Practical Workflow Scenarios 

Multiple Developers – Auto Branching 

• Every developer works in their own feature branch. 
• Merge Requests ensure that changes are reviewed and approved before being added to the main branch.   
• Pipelines validate and deploy after merges. 

Single Maintainer (“Super User”) 

• One central user manages branching, merging, and publishing. 
• Useful for small teams or pilot projects. 

Module-Centric Development 

• Teams build and deploy by domain (HCM, Payroll, CX). 
• Module-specific pipelines reduce risk and improve clarity. 

Multiple Projects vs Centralisation 

• Splitting into many small projects creates overhead—duplicate pipelines, access sprawl. 
• Better: consolidate per domain (e.g., one project for all HR modules). 

Merge Requests (MRs) 

• Critical for code reviews, governance, and maintaining an audit trail. 
• Ensure that only changes merged into the main branch go through pipeline-based deployments. 

Governance & Conflict Management 

• Avoid direct publishing from personal workspaces. 
• Always merge → validate in pipeline → publish via staging. 
• This prevents overwrites and race conditions. 

 Best Practices for Enterprise-Ready Redwood customisation

1. Define UX Strategy Early 

• Make sure designs follow Redwood standards and leverage Oracle’s Figma resources for consistency. 
• Ensure consistent patterns across modules. 

2. Reusable Components 

• Build modular UI elements with Oracle JET + Redwood patterns. 
• Avoid duplicating code across modules. 

3. Upgrade-Friendly Customisations 

• Never modify delivered objects. 
• Use VBS sandboxes and test quarterly updates in advance. 

4. Performance & Accessibility 

• Optimise load times, keep UI lightweight. 
• Ensure WCAG 2.1 accessibility compliance. 

5. Enforce CI/CD Discipline 

• Automate builds, testing, and deployments. 
• Use approval gates for production pushes. 

6. Adopt User-Centric Rollouts 

• Involve pilot groups early. 
• Personalise Redwood pages for roles, geographies, or business units via Express Mode. 

Bonus Demo Scenarios to Showcase in Enterprise Presentations 

• Rollback in Action → Show failed builds auto-reverting. 
• Merge Conflict Simulation → Demonstrate safe resolution before production. 
• Role-Based Access Control → Developers vs Maintainers with enforced privileges. 
• Approval Pipelines → Test deployments run without intervention, whereas Production requires explicit authorisation. 
• Audit & Compliance → Show traceability from commit → MR → pipeline → deployment. 

Final Word 

Redwood is Oracle’s UI of the future. Implementing it effectively via VBS requires

• Strategic planning – Your UX vision and enterprise goals align 
• Robust branching – Safe, controlled parallel development 
• Governed CI/CD pipelines – Automation with quality and oversight 
• Agile release readiness – Upgrade-proof and scalable design 
• Inclusive deployment – Performance, accessibility, and user feedback built-in 

Conclusion

Enterprise-Ready Redwood customisation in VBS hinges on

• Git branching and MR-driven workflows 
• Smart use of Express vs Advanced modes 
• Structured pipelines with validation & approvals 
• Clean separation of modules, access, and governance 
• Continuous UX alignment and performance focus 

Building Enterprise-Ready Redwood customisation with VBS is not just about UI tweaks—it’s about establishing an enterprise operating model that blends UX strategy, DevOps governance, and user adoption. This ensures your organisation delivers modern, resilient, and user-friendly experiences while staying future-ready. 

Author: Balaji Baskaran is an Oracle Technical Consultant at Fusion Practices