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 Security is behaving differently between Person Management and Directory

in Human Capital Management 2 comments

Summary:

Data Security is behaving differently between Person Management and Directory

Content (please ensure you mask any confidential information):

We have custom security roles with data security defined as custom SQL that refers to a department DFF. Historically the behavior between Person Management and new UI pages such as Directory or Quick Actions has been the same but now we’re seeing differences. The person management access is still accurate based on the person security profile and records are unavailable but the directory and quick actions are not and they can see records they should not see. Has anyone had similar challenges? We are aware custom SQL is not the recommended approach but it's the only solution that met our current business requirements.  

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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