DV email bursting - distribution lists?

Victor H

If we add a email distribution list. Will bursting apply individual security for each user?

Gianni Ceresa

@Victor H ,

I understand your question differently than Sumanth, and I would say no, individual security is not going to be applied.

The way I understand your question is if you add a single recipient being a distribution list, in that case the distribution to multiple users is managed by your mail system, not your analytics platform (that will have no idea about the fact there are multiple users behind your distribution list).

What Sumanth said applies if, and only if, you add all the recipients directly in the schedule as individual users, and not as a distribution list (therefore you are not going to use an email distribution list at all).

So, it depends what you meant by "email distribution list".

Sumanth V -Oracle

@Victor H - Yes, each recipient receives a customized data visualization based on their data access configuration instead of the data access configuration of the administrator user who creates the schedule.

This is mentioned in the product guide, please refer:

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/share-visualizations-using-workbook-email-schedules-preview.html#GUID-22A7474A-9989-43B8-A177-94B325FD90C3

Thanks!

Victor H

Thanks Gianni that was the scenario I was trying to describe.

Will submit an idea lab for this

Gianni Ceresa

With a distribution list (a real email distribution list), there isn't match that Oracle Analytics can do.

For the product, your email will be a single account, therefore only a single security profile can be applied to any delivery you will have.

Sending that email to multiple address will be done by the mail server, and nobody else will be aware of the emails that are behind (or included if you prefer) in a distribution list.

What was practical in "classic" with agents was to be able to use an analysis to get the list of recipients. In that way it would have been easier for you to replicate the members of a distribution list, also having a dynamic list of members (the analysis returning the recipients does execute a query every time the agent is executed, therefore the list of recipients is dynamic).

Your idea you plan to post could maybe go in that direction: be able to point to a dynamic list of recipients, based on a query or something like that (allowing you to add or remove addresses easily outside of Oracle Analytics, like in a database table, without having to edit each and every delivery schedule).