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.
Restricting access to sensistive EDI attributes
Summary
We want to restrict visibility of sensistive EDI attributes to a specific role when viewing others' informationContent
We have been given the requirement that a number of fields found in the Demographic Info region within Personal Details (some custom, some Oracle standard) are sensitive and therefore need to only be displayed to users who have a specific EDI role. Please see the table within the attached word doc for breakdown of the fields and screenshots.
I have tried to fulfill this requirement using HCM Experience Design Studio by creating one rule for Employee Self-Service (viewing own info) and one for EDI (viewing others' info). However, this is not giving the desired result because I am finding that all users who have HR access and therefore access to Personal Details, still can see all the sensitive attributes we are trying to restrict.
1