Currently if you schedule DV bursting to a distribution list the row level security is not applied.
If distribution lists could be defined within OAC then it would identify the individual users and apply row level security during bursting
Interesting idea in the idea lab. I wonder if it's more of a bug, security topic or enhancement. + @Alan Lee - Oracle-Oracle and @Adam Bloom-Oracle . In any case, I voted for it. Thank you @Victor H
+ @Sandeep S. Chauhan-Oracle
The bursting feature is only supported for users selected from OAC identity management system. Row level security is defined at the user level. Even though a distribution list may contain email addresses that are the same as users in the IDM, there is no explicit mapping. The best way to send to a group of users for bursting is to include these users in custom app roles that sit inside IDM.
We will make this more clear in the documentation.
@Alan Lee - Oracle-Oracle Thanks Alan.
Is this something that can be achieved in the current version?
How would we define these custom app roles? If the distribution list is defined in the client email server. how will OAC know the individual users for row level security?
Yes, this is supported in the current release. You can create a custom app role by following documentation here: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/configure-what-users-can-see-and-do.html#GUID-7547E519-07B5-414A-B664-771BA753B2FB
Assign users that you want for the scheduled delivery. Then you can specify the app role in the recipient field of the schedule.
Thanks Alan , this is a useful workaround but creating roles is usually done by totally different users.
I think it is still needed to add distribution lists in OAC as their one separate object, We already have many shell roles for folder structure access and would prefer to minimize them.
Customer has accessibility issues on the OAC classic dashboard. There are no landmarks exposed to screen reader users on the Homepage. When we drill down into a dashboard, it appears the tables are assigned as landmarks, but the landmark names are not descriptive. There are no standard landmarks for screen reader users…
I have an issue when upgrading OAS with one rcu schema only - BIPLATFORM. As I had db backups I was thinking I could use it for restoring my OAS datas. But this time it is not supported. My issue was 'validate failed: Migration checksum mismatch for migration 2.1.0.0.0' during executing of ua. Now I can only create a new…
We're considering rolling out the AI Assistant to more users, but as admins we've no real way of seeing how it's actually being used. Usage Tracking is great for logical and physical queries, but it doesn't tell us what questions people typed, which ones the Assistant couldn't answer, or where it picked the wrong column or…
Enhancement request Enable shared filter selections and saved states across all eight tabs of The Pulse – Ticket OAC report/dashboard. Filters selected on Opened Tickets should automatically apply to the other seven tabs, wherever the corresponding filter is supported. Current limitation Users must reapply their filter…
Enable OAC to import and map business ontologies to semantic models, providing shared definitions of business concepts, relationships, classifications, and rules across subject areas. Organizations often report on related data from multiple systems using inconsistent terminology and metric definitions. Ontology support…
