Define email distribution lists in OAC for bursting

Victor H

Currently if you schedule DV bursting to a distribution list the row level security is not applied.

https://community.oracle.com/products/oracleanalytics/discussion/22244/dv-email-bursting-distribution-lists

If distribution lists could be defined within OAC then it would identify the individual users and apply row level security during bursting

Benjamin Arnulf-Oracle

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

Alan Lee - Oracle-Oracle

+ @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.

Alan Lee - Oracle-Oracle

We will make this more clear in the documentation.

Victor H

@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?

Alan Lee - Oracle-Oracle

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.

Victor H

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.