Known limitations for controller-listener or drill-down relations
Lists of other known limitations on desktop computers and mobile devices for controller-listener or drill-down relations between widgets and dashboards on Cloud Application Business Insights.
- For a deployed dashboard that contains a drill-down relation, the target dashboard is displayed even if it is in draft state.
- For a dashboard that contains a drill-down relation, if the target dashboard moves into draft state or back to complete state, then such changes aren’t immediately reflected on the Set Relation window of the source dashboard. To view such changes, you must open the source dashboard again.
- For ITM assisted data definitions, when you select TIMESTAMP or Recording Time parameter, in drill-down or controller-listener relationship, then the widgets show Error in fetching data message. This error is because of a data provider restriction that doesn’t allow conditional data filtering based on TIMESTAMP or Recording Time parameter values.
- If you modify a drill-down dashboard, then you must republish the source dashboard. If you deploy the source dashboard, then the changes that are made to the drill-down dashboard are not reflected on Engine.
- Sankey, Circos, Sunburst, and Treemap charts support controller-listener or drill-down relation,
only if you add them as listener widgets or drill-down dashboards. However, these charts do not
support controller-listener or drill-down relation, if they are added as source widgets (controller
widget) in controller-listener or drill-down relation.
Similarly, Baseline and Box and Whisker charts support controller-listener or drill-down relation only if you add them as source widgets (controller widget) in controller-listener or drill-down relation.
- For a controller-listener or drill-down relation between a transformation widget and a normal widget, where the transformation widget is the controller widget, when you click a data point on the transformation widget, the title of the listener widget might not get appended with the value that you clicked in the controller widget.
- For controller-listener or drill-down relation set between two widgets, on the source widget, if
you click a
null
value, then the listener or drill-down widget goes into a loading state. - In a controller-listener or drill-down relation set between widgets that contain JDBC assisted data definitions, if you pass a Date type data value from the controller widget, then the listener or drill-down widget does not display any data and instead displays an error message.
- In a drill-down relation, if the drill-down dashboard contains multiple Map charts, then whenever you click a data point on the controller dashboard, the target drill-down Map chart displays data. However, all the other Map charts in the drill-down dashboard do not display any data points, unless those Map charts contain World maps.
- In a Topology chart, where the nodes are displayed as icons on the chart, if you set controller-listener or drill-down relation with Topology chart as a controller widget, then whenever the dashboard loads, none of the icons on the Topology chart are highlighted. However, the listener widget is loaded. It is the limitation of the chart library.
- In a drill-down target dashboard, if the data source is not available, then the mapping that was set earlier is not displayed. However, when the data source is available, the mapping is displayed.
- To view a drill-down URL that is attached to a real-time widget, if you click a data point on the real-time widget, then the URL opens on another tab. When you switch back to the real-time widget, the selection on the widget persists. The highlighted point appears to remain at the same position in the chart.
- On Safari browser, for Area, Line, and Stacked Columns dashboards with huge time series data, if
you set multiple controller-listener, drill-down, and cyclic controller-listener relations, then the
related listener widget or drill-down dashboard might not display correct data. Also, at times, even
if you click some data points, the related listener widget or drill-down dashboards might not be
displayed.
To work around this issue, you must maximize the controller widget, and then click a data point to view its related listener or drill-down data.
- For Area, Line, and Stacked Columns dashboards with huge time series data, if you set controller-listener, drill-down, and drill-down URL relations, with Area, Line, and Stacked Column widgets as controller widgets, and if you click outside the chart, anywhere around the Legend area, then a message that indicates you to zoom in to the timeline view is displayed.
- For a Baseline chart, when you set multiple controller-listener or drill-down relation, then the
related listener widget or drill-down dashboard might not display correct data. Also, at times, even
if you click some data points, the related listener widget or drill-down dashboards might not be
displayed.
To work around this issue, you must maximize the controller widget, and then click a data point to view its related listener or drill-down data.
- The Set Relation page does not open, if you delete the first controller widget in any of the multiple-controller single listener relations.
- On Engine, if dashboard nodes under different category nodes contain dashboards with the same name, and if you open all such dashboards, then only one dashboard node is highlighted.
- In multiple controller-listener relations, where a single controller widget is attached to multiple listener widgets, and each relation has a common listener widget, if you delete the uncommon listener widgets from one or more relations, and then save and reopen the set relations page. The relations are not displayed properly. The lines that connect the controller widgets to the listener widgets appear broken and the relations do not work.
- When you set a controller-listener or cyclic relation by using Complex Gauge chart as a
Controller widget, if you map inner gauge values with the listener widget, then the
controller-listener or cyclic relation does not work.
To workaround this issue, you must map the outer gauge values only.