Ability to share Data Flow with other users

Philipp Kaufmann-Oracle

Description

It should be possible to give read/write/execute access to a data flow I created to another user or an entire role.

This would be the same functionality as already available for data sets, projects and connections.

Use Case and Business Need

Data flows could be used to replace straight forward data load and preparation tasks that are not unique to a single user. For example a simple data movement from one DB to another doing some aggregations as part of a simple LoB analysis.

Currently, such scenarios are not feasible as only the user who created the data flow has access to it and therefore only this user can run or modify the data flow. If this user is not on duty (e.g. vacation, sickness) nobody can run or edit the data flow.

More details

The current version does not support granting access to a data flow to other users or roles.

Export / Import functionality will result in duplicate flows and added maintenance effort because flows have to be changed, exported, sent to the other team members and being imported by them.

Original Idea Number: 7d53dde946

Ingolf Lentzkow

That is what i miss.

E. van der Poel-Oracle

Hi,

this is also what we need for my customer who is using SSO (mandatory in production environment). And not only the DataFlows, but also the Sequences needs to be shared.

For maintenance purposes, it is necessary that (scheduled) workflows and sequences can be monitored by various persons.

Would be good to hear if this option will be added in the (near) future.

regards, Erik

Sylwester Dec-Oracle

Sharing content is the main goal of having BI solution. Without it it's a single user solution.

Bret Grinslade - Oracle Analytics-Oracle

This capability is on the roadmap.

nkhambampati-Oracle

Only the user who created the data flow has access to it and therefore only this user can run or modify the data flow. If this user is not on duty (e.g. vacation, sickness) nobody can run or edit the data flow.

Export and Import of DVA for data flows is creating confusions as each individual may customize their Data flow with a unique and the output may get impacted.

M_Kumaran

We Developer work on the same team and one would like to just run the other person flow or view or edit.

Angel Shipp

This option will definitely assist our developers as well.

Wayne Van Sluys

This would be helpful if employee leaves. only work around would be to have shared service account that is a native account

AHMED HAFEZ

yes this should be central and not user specific

Jonathan Michael Klinker

When a data flow becomes useful, it also becomes important. Important data flows stop being useful if they break and the user who created it is no longer available. This means that data flows shouldn't be used for anything important due to things like terminations, vacations, sick leave, etc. I don't like tell our users or administration that our nice new tool should not be used for important things!

Exporting/Importing data flows is a maintenance headache and is counter to the idea that data flows are accessible to non-technical people.

While is seems obvious to add the ability to add access to a data flow for other users and roles. I also suggest that every data flow should be accessible by a data flow admin role or BI Service Admin. Data Flows created by someone who has left the organization are lost forever. This again is a huge risk and advise users as such.

The same goes for Sequences and Data Replication objects.