Heatmap Reports in standard risk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2022 06:36 AM
When viewing the Risk Overview Dashboard (Risk > Overview) the heatmap charts (Inherent Risk Heatmap and Residual Risk Heatmap) no longer have numbers or borders. When you mouse over each box it does show the count of risks, so the underlying data is preset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2022 06:52 AM
Hi @Mike314 ,
Usually the Heatmap doesn't have borders (See my heatmap), however it does have numbers.
For that, Confirm under Style you have "Display data labels" set to True (checked) and You can enlarge the chart size to accommodate values or you can hover over a blank value cell to see its value.
For more about Heatmap reports follow this : https://docs.servicenow.com/en-US/bundle/tokyo-now-intelligence/page/use/reporting/concept/c_Heatmap...
Specially Styling options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2022 10:29 AM
I did confirm that display data labels box is checked on the Residual Risk Heatmap and the Inherent Risk Heatmap charts found under Reports > View / Run. I also changed the Chart size to large in case it was an issue with spacing. I am seeing the numbers in the View / Run report section but not the Dashboard. Also the numbers were appearing prior to the Tokyo upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2022 08:45 AM
We are experiencing the same issue. Since the upgrade to Tokyo, the Heatmap has become useless for visualization.
In San Diego, it looks like this.
San Diego Residual Risk HeatmapIn Tokyo , it looks like this.
Tokyo Residual Risk Heatmap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2023 05:43 AM
Can you try installing the latest version of the advanced risk plugin? And check if the issue still persists?