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.
Redwood Experience / Clarification on Migration process
Summary:
I would like to understand the situation a target env needs to be before migrating redwood pages from the dev enviroments to other NON PROD and finally prod envs.
Specifically
do we need to turn on in each individual environment redoowd? Do we need to set up the global configuration we went thru in the dev env in all the other environments, or the set up carries automagically into each target env?
When publishing a page - does the page need to be redwood enabled in the target env first?
does the person migrating the project from dev need to have the application developer or application admi role in the target env?
Tagged:
0