You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the new design, plugin pages using the new framework will be adding an "Associated Visualizations" table. This will list out all visualizations that are associated to a plugin resource, by collecting all augment vis saved objects that have the particular plugin resource ID, and pulling out the vis ID references. Initial support will include an 'Unlink' action, which will effectively delete the association by deleting the saved object.
Note all of these table details and actions taken are decoupled from the plugin. The only thing needed as input to render the table is a plugin resource ID. Because of this, we can implement and maintain this table in the vis augmenter plugin, which can then be consumed by plugins to add to their respective plugin resource details pages (e.g., anomaly detector configuration page).
Another advantage is that we may want to re-use this table at some point within the dashboards flows - for example, editing/stopping/deleting a plugin resource may bring up a warning modal listing out other visualizations associated with the particular plugin resource.
Example mock (with AD plugin): buttons in top right can be ignored
The text was updated successfully, but these errors were encountered:
ohltyler
changed the title
[Feature Anywhere] Add a plugin-consumable table to list associated visualizations
[Feature Anywhere] [Enhancement] Add a plugin-consumable table to list associated visualizations
Mar 1, 2023
Coming from #2880
As part of the new design, plugin pages using the new framework will be adding an "Associated Visualizations" table. This will list out all visualizations that are associated to a plugin resource, by collecting all augment vis saved objects that have the particular plugin resource ID, and pulling out the vis ID references. Initial support will include an 'Unlink' action, which will effectively delete the association by deleting the saved object.
Note all of these table details and actions taken are decoupled from the plugin. The only thing needed as input to render the table is a plugin resource ID. Because of this, we can implement and maintain this table in the vis augmenter plugin, which can then be consumed by plugins to add to their respective plugin resource details pages (e.g., anomaly detector configuration page).
Another advantage is that we may want to re-use this table at some point within the dashboards flows - for example, editing/stopping/deleting a plugin resource may bring up a warning modal listing out other visualizations associated with the particular plugin resource.
Example mock (with AD plugin): buttons in top right can be ignored
The text was updated successfully, but these errors were encountered: