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.
What is the best practice to deploy changes in VB Studio to other instances after testing?
Summary:
What is the best practice to deploy/migrate changes in Visual Builder Studio to other instances/production after testing is finished?
Content (please ensure you mask any confidential information):
- Multiple team members are working on different pages in the HCM extension with different go-live dates
- Based on the documentations and posts, my understanding is that we need to work:
- In 1 project with the HCM extension
- In multiple workspaces
- In multiple branches
- Questions:
- What is the best practice to do the testing in our test instance, while migrating the already tested changes to other instances?
- How should we pull over only the tested changes (from the given branch)?
Tagged:
1