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.
Data Obfuscation/Purge and retention policy - Process for identifying 'affected records'
Summary:
We have deployed HCM in more than 15 counties and trying to ascertain how best to store the 'retention' period that can be used to initiate the 'trigger' to run the data obfuscation/ disposal process
Content (please ensure you mask any confidential information):
At present the most viable solution appears to create a UDT to capture the specific legal period by country, which is then applied to a scheduled report to identify the affected employee records that is up for deletion.
This would be used in addition to setting up two policies in the Personal Removal tool and HDL
Version (include the version you are using, if applicable):
1