Mark a widget as "Inactive" or "Out of order"

[JayJohnsonWashoeCounty]

Add an "out of service" flag to the widget configuration.  On the dashboard, this would then display a custom message explaining the outage for any of the widgets or stacks that are having problems.

USE CASE  -- On our existing dashboards we sometimes have widgets or event entire groups/stacks that encounter a technical problem that prevents them from displaying.  This can be a problem with an underlying table, something that causes a re-design of a work process, etc.  Rather than removing that widget and then having to re-create it later, it would be useful to mark it as "inactive" or "out of service", so that once the issue is resolved we can just put it back in service by updating that item's status.

This differs from the "No Data" configuration, in that the connection to the data might still exist and it would display, but because of the issues we are working on, we don't want to display the data.

[jcarlson]

Sounds sort of like the "pending" bin in Experience Builder. This would be a fantastic addition to Dashboards.

[patrickb]

This idea has failed to gain traction, so we will close it with the following information .... Data-driven elements in a dashboard will show a yellow 'data source error' triangle on the lower left when there is an issue. If the underlying layer has a refresh interval set, the dashboard will poll the layer periodically and should self-correct. 

Also, dashboard layouts are designed to take up 100% of the screen. Marking an element as 'inactive' might not work under those constraints, but one thing you can do it set an element's width or height to 0 so that is is still in the layout, but will not draw. (We don't necessarily advise this, however, and doing so with a map element can lead to some undesired behavior in the dashboard elements that use its layers as data sources).