Learn about the new Oracle Fusion AI Agent Studio on April 15, 2025 at 8:00 am PT - Register Now
Get Started with Redwood for Oracle Cloud HCM Begin Now
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.
Migrate Redwood Project from TEST to PROD pod
Summary:
Hi @John Rhodes-Oracle , @Shay Shmeltzer-Oracle
While migrating our changes to another pod, we have the questions below.
- We initially had a separate project for our Pods for POC purposes. When we migrated from EEFJ-TEST(Project name: EEFJ Project) pod to the EEFM-TEST(Project name: EEFM Project) pod, we realized that even though the migration was successful. We could see changes in the UI via end-user login, the business rules were not visible in EEFM unless we used the “
EEFJ project”. Is this expected? - Given the above is true, what happens when we have Production to Test(P2T) refreshes would the “EEFJ Project” be overwritten/removed? How to export and import projects for later if such things happen.
Tagged:
0