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.

What are the best practices for VBS projects

Summary: We are planning to implement multiple pages in redwood and will be using VBS to customize multiple pages. What are the best practices for projects?

  1. Should we have a single project for all pages irrespective of module? Or should we have multiple projects for different modules i.e. 1 project for Core HR pages, 1 for Payroll pages, etc?
  2. If someone publishes learning pages from project A and someone tries to publish Core HR page from project B, will these override each other's changes?
  3. How do we update the repository in Project B, so it picks up the latest changes published by Project A?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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