AI beyond HRMS. Meet DelveAnt, our AI-native CRM for modern sales teams. Get Early Access for FREE
Found 1065 results.
AI beyond HRMS. Meet DelveAnt, our AI-native CRM for modern sales teams. Get Early Access for FREE
Discover how AI-powered HR solutions are transforming workforces – join us in London to enhance employee
experience and drive business growth. Register now!
Learn how to create and manage branches in Oracle Visual Builder Studio for Oracle Redwood Experience to safely develop, test, and deploy Redwood customizations.
Modern HR applications built on the Oracle Redwood Experience require a structured development approach to ensure stability, scalability, and seamless updates. When making UI customizations or implementing enhancements, developers must work in an isolated environment that prevents unintended changes to the primary codebase. This is where branching becomes an essential development practice.
By creating branches in Oracle Visual Builder Studio (VBS), developers can safely build, test, and refine Redwood extensions without affecting the main application environment. Branching enables parallel development, better version control, and a controlled process for validating and merging changes into the main branch.
This step-by-step guide explains how to create, switch, and merge branches within Visual Builder Studio when working with Redwood applications. Following this structured approach helps development teams maintain clean code management, ensure smoother deployments, and support continuous innovation within Oracle HCM environments.
Before creating a branch in Redwood, ensure the following:
1. Access to Visual Builder Studio (VBS)
2. Required permissions to:
3. An existing Git repository connected to Redwood
4. Familiarity with:
5. A configured development environment in VBS.
Fig 1: Creation of Workspaces
Fig 2: Specify the workspace name
Fig 3: Go to the workspace
Fig 4: select Switch Branch Sandbox.
Fig 5: Enter the branch name you created
Fig 6: Access Jobs
Fig 7: Switch to your created branch
Fig 8: Create Merge Request
Fig 9: Deploying changes to production
Implementing a structured branching strategy in Oracle Visual Builder Studio provides several operational and development advantages for organizations working with Redwood extensions.
1. Safe and Isolated Development: Branches allow developers to work on new features, UI enhancements, or bug fixes independently without impacting the main application environment.
2. Improved Code Stability: Since all changes are developed and tested in separate branches, the main branch remains stable and production-ready at all times.
3. Better Collaboration Across Teams: Multiple developers can work simultaneously on different tasks using separate branches, enabling efficient collaboration across development teams.
4. Streamlined Testing and Validation: Branches provide a controlled environment to test changes using build jobs such as hcm_extension_package, ensuring updates function correctly before merging.
5. Efficient Version Control: Branching allows teams to track development changes, manage multiple versions of enhancements, and maintain full traceability of code updates.
6. Controlled Deployment to Production: By using merge requests and structured workflows, organizations can ensure that only validated and approved changes are deployed to production.
7. Faster Development Cycles: Developers can build and test new features in parallel without waiting for other updates to complete, accelerating innovation and delivery timelines.
8. Strong Governance and Change Management: Branch-based workflows support structured development practices, helping organizations maintain governance, audit trails, and development standards.
Ready to streamline your Redwood customization and development workflows in Oracle Visual Builder Studio? At Kovaion Consulting, we help organizations implement structured branching strategies and best practices for developing extensions within the Oracle Redwood Experience.
Our experts support teams in configuring development environments, managing Git branches, optimizing build pipelines such as hcm_extension_package, and implementing efficient merge and deployment processes. By establishing a well-governed branching strategy, we help organizations reduce deployment risks, improve collaboration across development teams, and maintain stable production environments.
Partner with Kovaion to modernize your Redwood development lifecycle with expert guidance, proven implementation frameworks, and continuous support—ensuring your Oracle HCM environment remains scalable, secure, and ready for future innovation.
Creating a branch in Redwood using Oracle Visual Builder Studio is a critical step in maintaining a well-structured development workflow. By isolating development work from the main branch, teams can safely implement enhancements, fix issues, and test updates without disrupting the production environment.
A proper branching strategy also improves collaboration, simplifies testing, and ensures that all updates go through a controlled validation and merge process before deployment. This structured approach helps maintain code quality, ensures traceability of changes, and reduces the risk of errors during production releases.
By adopting disciplined branching practices within Visual Builder Studio, organizations can support faster innovation while maintaining the stability and reliability required for enterprise-grade Oracle HCM implementations.
Author: Smruti Samruddha, Oracle HCM Cloud Consultant.
Connect with us for End-to-End Implementation, Enhancement, Updates, and Support for Oracle HCM.
Read MoreThis website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.
