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.
Controlling and monitoring customizations done through Visual Builder studio in Redwood:
Summary:
We are planning to have a control on who can publish the changes in the mainline in Redwood and to be able to see all the customizations/configuration changes that has been deployed to the instance using VBS in the past by all the other users/from different Workspaces. This would be crucial to manage the configuration from getting corrupted due to unwanted deployments that can be done by various users having access to VBS(example users from customer end during development phase).
With the details mentioned in the document below:
It seems that individual users need to add the reviewer for each of their project
0