nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Rename the visualization "Dashboard Filters" in DV

Gianni Ceresa

DV has workbooks and canvases and visualizations, "classic" has dashboard and dashboard pages and analyses and dashboard prompts.

An effort has been made since the beginning of DV (VA back in time) to not use the same name.

Why to start confusing people now?

DV doesn't have dashboards, there is nothing called dashboard in DV, so why is there a visualization named "Dashboard Filters"?

It should be named "Canvas Filters" to be consistent with naming and not confuse users, mostly users who knows "classic" and will start thinking a "Dashboard Filers" means there is a cross link with "classic" dashboard.

Names should not generate confusion in users.

Find more posts tagged with

Declined

Status: Declined

Comments

Gabby Rubin-Oracle

I can't answer this without getting into an apparent minor danger zone.

The "canvas" terminology is a design time terminology for the surface on which the author creates a Dashboard, where the consumed content is a Dashboard. The model is that "painting on a canvas" results in a "Dashboard" with a very on-the-nose analogy to "a painter paints on a canvas, resulting in a painting".

This brings me to the danger zone of "that's even more confusing because it is not a Dashboard object." well, I would argue that for the consumer, it is a Dashboard. Our guiding principle was that a consumer does not care about the tools used to create the end product; a Dashboard is a definition of content, not the underlying technology artifact. On the other hand, the author might need to differentiate its tools and directly call out what will be used for specific tasks.

As to the Dashboard Filters visualization name, starting with the word Dashboard. As I stated above, the author creates a Dashboard on the Canvas; as such, the Dashboard Filters are an element of the outcome. With respect to the word Filter. We did consider Prompts but decided on filters because:

They do not prompt.
The consumer-recognized term is filter/selector/slicer.
We might eventually want to introduce prompts, and they might not be related to this specific viz.

I don't expect everyone to agree with our logic; most probably never noticed that the term Canvas was removed from the consumer experience. It is relatively easy to communicate new features, it is harder to communicate concepts and mindsets.

Michal Zima

@Gabby Rubin-Oracle The explanation you have provided here make sense and I understand, that it is much more harder to explain/communicate concepts than just launching new features. But I am convinced that it should be done - ideally in a standard documentation set (https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/index.html or https://docs.oracle.com/en/middleware/bi/analytics-server/user-oas/index.html). This will help quite a lot and will leave very little space for potential confusion.

Thanks

Gabby Rubin-Oracle

Noted, we will review how we can incorporate that in the future.