You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

VBS Main and Feature Branches Best practice to plan for HCM Sprints, P2Ts and Upgrades

in Visual Builder Studio for HCM

Hi @John Rhodes-Oracle appreciate your Lets talk Tech and other sessions covered on VBS Feature branches topic and your guidance on customer connect regarding these topics.

Enclosing below a specific scenario to review if it is a correct approach for Feature Branches, Main and Release branch across Sprints, P2Ts and Upgrades across multiple team members.

Lets consider VBS Extensions scenario as below -

Main Branch–

Currently main has VBS extensions developed in 25A for Talent but it is not yet deployed to PROD. HR testing is in progress and target to wrap up before June 2025 (25B).

Question

We understand that this content in main though not in PROD will not be impacted with any upgrades/P2Ts.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!