Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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
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.

Best practices to create Project in VBCS for multiple teams under HCM

Summary:

Under HCM we have different teams Core HR, Talent Management, Payroll working on Redwood changes which have different timelines to migrate their changes to UAT and Prod. Also, some teams want to conduct testing on dev13 and others want to continue testing on dev11.

Shall we create separate 3 Projects in VBCS or create 1 Project for all 3 teams.

If we create 1 Project, all team code changes will be in main branch. Then if we just want to deploy Payroll changes alone to dev13 from evac-test on a certain date, How we can control that?

Content (please ensure you mask any confidential information):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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