Give Admins access to data flows created in OAS DV as a default

Angel Shipp

Organization Name

Verizon

Description

We would like admins to instantly have access to data flows upon creation in OAS DV.

Enable admins to view, edit, and even delete data flows as a default when data sets are created. 

Use Case and Business Need

This would enable better management of the platform especially since data flows cannot be shared with other users at the moment.

More details

Currently, data flows cannot be shared with other users. Whenever there are errors with data flows, admins are not able to troubleshoot and assist users. 

Original Idea Number: 85dbdc5408

Andrew Desalme-Oracle

Our customers are also asking for this, currently it's difficult to manage datasets and data flows in a large organization.

Cameron Zapf

We would love for this to be implemented as well. Additionally admins should be able to manage all scheduled data flow jobs/schedules regardless of whether the user has shared them or not.

Adam Bloom-Oracle

We have features in the pipeline for admins to manage objects e.g. change ownership. We also have features in the pipeline to add access controls for Data Flows. I can't give a release or date, but these features are on our roadmap.

Michal Zima

Changing the ownership (or more precisely changing "namespace" of DV objects, which is part of unique identifier of DV object) of DV objects (connections, data sets...) especially after deployment of those objects on target OAC/OAS environment via DVA package is critical requirent for us - so we look forward to have it implemented quite soon.

Chris Bo

We would also like this enhancement for the OAC Instances.

Bret Grinslade - Oracle Analytics-Oracle

@Michal Zima i don't think we have any plans to change "namespaces" for objects. Once they are imported the namespace is really just part of the object identifier. What would changing a namespace do for you?

Michal Zima

@Bret Grinslade - Oracle Analytics-Oracle -as per your question - look at my Idea: https://community.oracle.com/customerconnect/discussion/604674/preserve-namespace-owner-of-ds-connection-during-dva-package-deployment#latest - here you will find the justification, why having the ability to change namespace is important for us - it overcomes the behaviour of import of DVA package, which does not preserve namespace of data sets/connections imported via DVA package from "source" environment.

So if this would be accomplished (DVA package import would preserve namespace of DV objects from source OAS environment, even in case when import is performed by another user - not the owner of objects from source environment, but Administrator - which can be different persons), changing namespace afterward would not be required (I am aware of the fact, that namespace is part of unique identifier of DV object).

I hope, our relationes behind of this requirement are clear now.

Rgds

Michal

Gabby Rubin-Oracle

Admins can now access the artifact in case they want to change ownership or delete. To edit they first need to take ownership.

Angel Shipp

@Gabby Rubin-Oracle , this is good to know. Is there documentation on this capability? Also, is this available in OAC only or also in OAS?

Bret Grinslade - Oracle Analytics-Oracle

The documentation is here: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/manage-content.html#GUID-96E84E17-E137-45DD-8110-F674B218E671

It was released in the March OAC update meaning it should be in the next release of OAS.

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acswn/index.html#ACSWN-GUID-63D00C9F-6C2C-4023-A962-E5531369A168