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.

Data Masking in Non Prod Instances

edited Mar 25, 2021 7:39AM in HCM Integrations 5 comments

Content

Hi Team,

Can you please share insights on the best practices which you are following for non prod instances post P2T refresh? Specifically, I am looking for your inputs on:

  • Are you using Oracle's data masking service?
  • If yes, is there any documentation around it other than Oracle Applications Cloud - Data Masking Standalone Service Entitlement (Doc ID 2092389.1)
  • If you are using a custom process, what all data is considered for data masking?
  • What is the approach and time taken for data masking post P2T refresh?
  • Any disadvantages which you see post data masking?

Thanks.

Version

21A
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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