Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

What is the recommended action plan to enable Redwood in HCM?

Summary:

Recommended Action Plan for Redwood migration


Content (please ensure you mask any confidential information):

One of our customers wants to start the migration to Redwood screens for HCM modules, but we would like to know what is a recommended action plan? In a discussion with Oracle team, we commented as a possibility considering the MVP concept, where we plan a staggered migration, where we will start in non-productive screens and after that (when the Redwood screens have stabilized) migrate the Redwood screens in non-productive environments, all this thinking in not affecting the productive processes.

I would like to know your opinion about this action plan, and if possible, if there is any documentation that can help me to justify this idea?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!