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.
Managing Redwood development across environments on different releases
Summary:
Managing Redwood development across environments on different releases
Content (please ensure you mask any confidential information):
We are now in the middle of our move to redwood and have many pages now live in production, and we also many pages we have in a 'Dev' branch conducting testing of other pages.
The environment where we have configured the 'Dev' branch, has had the 24D release today, where as all our other environments have still got 24C, including the source visual builder environment. (so my understanding is I cannot migrate changes into here now and will need to wait for my other pods to also receive 24D?)
0