Strongly agree. It can be extended also to other object types that may have meaning only in the context of others (e.g. an analysis guided from prompts defined in a dashboard). So, in general, an administration console that allows the definition of the visibility (by roles) of the different object types in the DW Home page…

This kind of project-scope setting are much needed. With little effort, lots of manual activities (e.g. resizing font in excel after each export) can be avoided.

Fully agree. Much needed. Very similar idea already present in the lab (DV Home Page ...)

For specific applications like HR or health, it may be a needed feature. Details are to be defined (since there could be different authentication components, DV project can be embedded in other applications, ...).

Limit export feature by roled should be already possible in the manage privilege section of the Administrative console, but this apply only to Dashboards and Analysis, I don't think that it involves also DV, which is much less configurable regarding privileges. Must have ...

Very needed features, that will become even most important in the future.

I absolutely agree. This is one of the most important pieces of information customers need to have about user's activity on the system, and it's already present in the logs.

Another point for this request: * for "Oracle EPM" connections, the filter on any dimension doesn't show any value if it is set to AUTO, you have to manually set it to NONE to make it present the list of values. And you have to repeat this setting for each filter (which tend to be many when connecting to a typical EPM…

Completely agree. In this section, fine-grained privilege and access configurations (like in daskboard/analysis) should be possible, to better control, beyond the macro-roles author/viewer, what product DV features are available to each application role, what section a role is allowed to see in the home page, and so on…

Very welcomed!

Needed step forward for this integration functionality

Needed step forward for this integration functionality

Agree. Even for us this is a great limitation.

It's not complex to drag another dimension from the data model on the left, but this can be useful in the constant shift toward putting more features on the canvass and let the user ignore other screen areas (filter bar, which I think should be given the possibility to hide, data model, etc.), like has already been done…

In the perspective of DV as a unified interface, it makes a lot of sense, to blend self-service capabilities and consistency, where needed, with centralized definitions.

Reasonable. It may be needed. The administrator or current owner can change. This event should be logged for audit purposes. Don't know if an acknowledgment is needed for both the old (if an admin performed the change) and the new owner.

I think it's already planned, but is a must-have feature for Gen2 OAC.

We also have experienced the same. A "need to be solved" issue.

Absolutely! More than ever now that the long-awaited list box visualization (that let you put filters within the canvas) has been released. It should be possible to hide the bar only where no global filters have been defined, to avoid losing context (the filter's values) that is not visualized elsewhere.

Agree. This is an underlie of a fundamental choice: if DV has to become the new, unified, UI for analytics (so a development environment, with all the interactions within and between canvasses), then this and other features requested in other ideas, that are characteristics of OBIEE and Oracle Cloud BI, has to be ported…