In a nutshell
Redwood enhances the customization capabilities of Oracle HCM Cloud, while VBS introduces a more structured development framework to fully leverage its potential. Consequently, the success of a project depends above all on a clear operational model, defined before development begins.
Within the ecosystem Oracle HCM Cloudecosystem, Redwood modernizes the user experience and transforms the way interfaces are customized. To tailor this new experience to the needs of each business, Oracle provides Visual Builder Studio (VBS), its development and extension platform.
For businesses, this raises some very practical questions: How can existing processes be adapted? Is it necessary to revamp the internal organization? And how can deployments be secured?
Abderrahmane LAFTISSI, an Oracle HCM consultant at SQORUS, shares his observations from the field and his tips for mastering Redwood and VBS.
How do Redwood and VBS change the way Oracle HCM is customized?
Redwood and VBS are two distinct concepts. Redwood is the new user experience shared by all Oracle Fusion applications: modern, streamlined, and intuitive screens designed to simplify the day-to-day work of employees, managers, and HR teams.
Visual Builder Studio complements this. It is the tool that allows you to tailor this experience to each company. It is used to modify existing Redwood pages (add a business rule, set a default value, make a field required, or hide it) and, when necessary, to create new experiences. This ranges from simple adjustments to more advanced development.
Abderrahmane LAFTISSI
Oracle HCM Consultant
With Redwood, we’re taking a new approach: it’s no longer just about adapting screens, but about evolving the user experience within a structured development framework that closely aligns with the company’s specific needs.
This new model requires new skills. Teams must be proficient in version control with Git, working with branches (local and remote), and deploying from one environment to another.
In practical terms, what are the key steps for setting up and initializing a VBS project?
A VBS project isn’t something you can launch with just a few clicks. You have to create it, link it to the Oracle HCM environments, and organize it systematically to avoid conflicts. The process consists of five key steps.
- Audit of the Existing System: The first step is to analyze what already exists before any configuration takes place. Are there any VBS projects? Are there any extensions to standard pages or new applications? What work methods have been used? The answers will indicate whether it’s better to start from scratch with a new project or build on what already exists.
- Client Scoping: This step involves working with the client to clarify how their environments are used, their versions, their point persons and developers, as well as their deployment process.
- Defining the operational model : This is the most important step. Who develops, who validates, and who deploys? How do developments move from one environment to another? Everything must be clear before moving forward.
- Opening Access and Roles: Access is granted only after the framework has been defined and approved.
- Communication: The project team meets to present the model and the organizational structure. Construction begins at that point.
“The operational model is the key to success. Without clear rules about who does what, it’s like a kitchen where everyone works without coordinating: teams end up getting in each other’s way, and mistakes pile up. VBS provides a framework, but the way we operate still needs to be defined so we can work together effectively.”
Accelerate Your HR Projects with Redwood
Would you like assistance in ensuring a smooth migration and deployment of your Oracle HCM Redwood projects? Contact our SQORUS experts for a personalized session.
How do you balance simple customizations and advanced developments in VBS?
The choice of customization level depends primarily on your needs. Declarative business rules make it possible to address many scenarios without resorting to custom development: setting a default value, hiding a field, making it required, or adding a consistency check. These solutions are easier to maintain and minimize the risks associated with platform updates.
The main focus is on advanced developments: specific logic, code, or calls to external systems. VBS’s advanced mode builds on the capabilities of Express mode and expands upon them. These developments may be appropriate when justified by business needs, but they require an assessment of maintenance risks and the potential impacts of future updates. The integrator’s role is also to anticipate these risks and plan for fallback solutions to ensure business continuity.
“The real question isn’t whether we can do it in VBS, but whether we really should.”
What impact do Oracle updates have on Redwood extensions deployed via VBS, and how can we ensure the reliability of non-regression testing?
In Oracle HCM Cloud, updates follow a quarterly cycle. This is standard practice for SaaS, which requires anticipating the impact on extensions.
The VBS extension model provides a better framework for customizations than some legacy approaches. By leveraging the mechanisms provided by Oracle, the impact of platform changes can be better managed. Specific customizations require increased vigilance and appropriate testing.
“Updates to Oracle HCM are part of normal SaaS operations. The challenge is not to eliminate all risk, but to detect regressions early enough. This requires a rigorous testing methodology, in which automation can play an important role.”
After each update to the test environment, teams can run targeted scenarios to verify that the customizations still work as expected. Automation makes it easier to repeat these checks during each update cycle.
What challenges do you see clients facing when implementing Redwood/VBS, and what support approach do you recommend?
The first pitfall is replicating the existing setup exactly as it is: some companies activate the new interface and carry over their old customizations. In doing so, they miss out on what Redwood has to offer—a redesigned user experience. Yet this is an opportunity to revise HR workflows, simplify them, and turn the tool into a daily ally rather than a burden.
The second pitfall is starting without a clearly defined operational model. Without specific rules, multiple people may work on the same page, overwrite each other’s changes, or deploy changes to production without prior validation. The result: conflicts, frustration, and a significant waste of time.
To avoid these pitfalls and make Redwood a catalyst for transformation, a structured support is necessary. It covers both technical skills—particularly version and branch management—and team organization, on both the integrator’s and the client’s sides. The rigor applied at the outset translates into maintainability later on, giving teams the time to focus on the value they deliver to users.
Abderrahmane LAFTISSI
Oracle HCM Consultant
Redwood should not be viewed as simply another interface to enable. It is an opportunity to rethink HR processes and simplify employees’ day-to-day work. A more seamless experience can also help build their trust in the tool and encourage its adoption.
Do you have a project? A request? Any questions?
FAQ
What is the difference between Redwood and Visual Builder Studio?
Redwood is the new user experience shared by Oracle Fusion applications. VBS is the tool that allows you to tailor this experience to the specific needs of each company, from simple adjustments to advanced development.
Do Page Composer and Transaction Design Studio still work with Redwood pages?
Page Composer and Transaction Design Studio apply only to standard responsive pages. Once pages are migrated to Redwood, VBS becomes the only supported tool for customizing them.
How do Oracle's quarterly updates affect VBS customizations?
Each update may affect the deployed extensions. The VBS extension model better mitigates this risk than historical approaches, but non-regression testing is still required after each cycle.
