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.

Quarterly patching testing window

edited Apr 10, 2017 4:45PM in Human Capital Management 5 comments

Summary

Info required on quarterly patching test window

Content

Hi There, 

We are on Rel 11 of Oracle Cloud HCM and having plans to upgrade to Rel 12 as its GA.

Our customer always perform end to end testing of all the monthly patches applied in our environments. As soon as the release notes are out for the monthly patch bundle , our team will do an impact analysis on the same. After the patch is applied in the lower environment, all the core business flow test cases across modules along with the changes mentioned in the MPB release notes will be tested. our team will ensure, the patch bundle is not impacting any core functionalities before the patch is applied into production which is on the third week of the month.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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