Genesys Dashboards
We've added links onto the Genesys Cloud Conversation Summary dashlet to enable easy navigation to Genesys related reports and conversation records. To make navigation even faster, Administrator and Normal user types can enable auto-start on the dashboard they create.
Note: This feature is not available to Dashboard Only users
Genesys Cloud Conversation Summary dashlet
Links are available from the following places on the dashlet:
| Link | navigates to |
|---|---|
| Conversation Records | Genesys Cloud Conversation Data grid |
| Stream Quality | Mean Opinion Score Distribution report |
| Agents | License Usage Trend report |
| Configured agents | License Capacity report |
| Logged in agents | VSM-Everywhere Devices grid |
Genesys Trunks Summary dashlet
Beside the Trunk Base name there is a link to the Trunk Group Call report.
Alarms Overview dashlet
On the 24 hour Summary panel beside the Alarm Name heading you will find a link to the Alarms report. This dashboard and report are technology agnostic so can be used for any product.
Microsoft Teams Call Summary dashlet - navigation to reports added
Note: This feature is not available to Dashboard Only users
On the User Feedback pane, we've added a link so you can now navigate to the Session Quality User Feedback Summary report.
On Modalities, we've added a link so you can now navigate to the Microsoft Teams User Activity report.
Bug Fixes
In the new Dashboard service, the Alarm Summary dashlet was reported as slow to load. We've made some improvements to make loading faster. Thanks for your feedback!
User Feedback grid was not populating with the Feedback rating information even though they were showing in Microsoft Teams Records grid. This has now been fixed.
User Feedback that is tagged as 'Not Rated' is now classified as Feedback=No in the Microsoft Teams Call records grid. This makes finding genuine feedback easy. (Bad, Poor, Fair Good, Excellent)
On the Microsoft Teams Call Summary dashlet, the Audio devices count for Uncertified devices was including "null". These are now excluded. Note that devices are per call session so do not correlate directly to unique participants. For example, one participant could join a Teams call using both their mobile phone and their laptop. This is counted as four audio devices and two platforms. Audio devices are split into the capture device (microphone) and render device (speaker).
Newly on-boarded customers (less than 30 days) could not run the Session Quality User Feedback report using the Month selection button. This has now been fixed and the report runs and shows zero data for the days before they were on-boarded.
When the BP was running a report for a Customer in a different time zone to them, the Microsoft Teams Device Usage report was not rendering a chart on the pdf although there was data in the csv file. This has been fixed.
Syslog files were creating multiple folders for the same equipment in Files and Folders. This has now been fixed.