This is now "delivered" by Oracle

Thank you for supporting this post

This can be closed

To follow up on this idea, the allowed ACL size in OACS classic is '64'. For clients with more than 64 roles, it creates issues managing access to catalog effectively, especially if they are implementing multiple pillars - FIN/HR. A catalog group functionality, like in FA OBIEE, would reduce the number of roles to be…

Thanks for liking this post, we will update it once we receive the latest information from Oracle

Thanks for liking this post, we will update it once we receive the latest information from Oracle

Thanks for liking this post, we will update it once we receive the latest information from Oracle

Hi, it is possible to get HR security tables into DBCS or ADW and mimic row level security in OACS. You can contact me directly if you want at matt.van.asten@pwc.com

Here is a similar Idea Lab, but at the Administration > Manage Privilege level of OBIEE: https://cloudcustomerconnect.oracle.com/posts/2d0c3ed91f

Agree with this being a requirement for clients and to add consistency across Oracle platforms. For example, it is possible to add a company logo in OACS catalog. We went through the process of confirming that the logo in OBIEE is still not a feature in FA 20D. It was confirmed via an Oracle SR and the feedback was to log…

Agreed on the Idea Lab. It is especially important for clients that implement various Oracle Pillars. For example, if a client implements Oracle Cloud ERP and Oracle Cloud HCM, they have developers on teams that should NOT have access to each other's data. There should be a way to separate the Data Model Data Source.…

This is a great idea lab that would help OACS teams build capabilities required to our clients and for consistency with FA reporting tools