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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Organization of changes to redwood pages from multiple users
Summary:
Function required / best practice for working on extensions/ changes to redwood pages while multiple users work on the same pages.
Scenario:
HCM Application with multiple functional areas (Global Core, Recruiting, Performance) is being implemented → 1 Project created for Redwood Adjustments in VBS to make sure GIT-changes from different streams can be handled via merge requests / conflicts resolutions.
Users work in individual workspaces on redwood pages (via Edit Page in Visual Builder Studio button) and publish changes to main-branch.
User1 and User2 both start editing a page at the same time (e.g. change assignment). For both, individual workspaces with copies of main are created.
0