Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
Concerns on using multiple Fusion instances for VBCS project development and deployment to PROD
Summary:
Hi Team,
We are using sprint releases approach for switching to Redwood from RUI. For example, we used Dev40 as source(24C) for Release 1 where in we went live with X number of pages across modules. In Release 2 we plan to go live with Y number of pages using the same project in the same instance (dev40-24D). There is a concern regarding release 3. We plan to keep using the same instance but dev40 is in the production cadence. We plan to start release 3 with 25A version but 25A release is planned post Release 3 start date and prior to
0