Summary | Description |
| SLA is calculated based on a hardcoded formula for CCX | SLA = (Calls Handled/Total Calls) x100 |
| For CCE, a call that gets abandoned by the customer after being routed to an agent is not treated | A call that gets abandoned by the customer after being routed to an agent is not available for reporting purposes and thus, is not shown in the EF dashboards. However, this may affect the SLA of the skill group. |
| If an agent is on an internal call, those calls stats would not be available for reporting on the skill group level | If an agent is on an internal call, those calls stats would not be available for reporting on the skill group level. For example, if the agent is on an internal call and in Not_Ready state, this will not be reflected on the skill group and would consider that the agent is ready on the skill group. |
| Only inbound voice call statistics are reported on the dashboards | Only inbound voice call statistics are reported on the dashboards |
| The fixed range of the speedometer display type is from -100 to +100 | The range of the Speedometer is updated from -100 to +100 (going from left to right, i.e. Red - Green). |
| Any changes made to the dashboard are not automatically reflected on the dashboard link | Refresh the browser tab to reflect any changes that are made to the dashboard configuration (changes to the name, background color, company logo, dashboard gadgets (added, removed, updated)) |
| Gadgets are not resizeable | Gadgets added in the dashboard are of the fixed sizes and cannot be resized. |
| Templates are not resizeable | Templates are not resizeable. The user has to choose from fixed templates |
| Free Dashboard Design grid not available to create custom dashboard templates | Dashboards can only be created following one of the predefined dashboard templates. Users cannot create customized dashboard templates for now. |
| The user-uploaded Company logo is not applicable to the final Dashboard view | The logo uploaded by the user is displayed across all admin portal pages only and is not applicable to final dashboard views. |
| Large gadgets in small boxes might disturb the UI | Users should avoid plotting the gadgets with large visualizations especially the Bar/Line charts and data tables on the dashboard templates having small boxes. |
| Refresh the dashboard final link manually in case of a network glitch, | In case of a network glitch, manual intervention is required to refresh the dashboard view |
| Refresh the dashboard link to see updated or removed gadgets from the dashboard | If the user changes or removes and adds another gadget in a dashboard while the final dashboard link is already opened on a separate window, the user would need to refresh the page to see the updated gadgets. However, the real-time stats are updated automatically without requiring to refresh the page. |
| Refresh the final link to see the updated logo on the Dashboard fullscreen | Refresh the final link of the dashboard to see the updated logo on the Dashboard fullscreen. |
| Dashboard Template once selected cannot be updated later | Once the dashboard template is selected, the dashboard is created with a default name. The user cannot later change the template. To change the template, delete the dashboard and create a new dashboard with the desired template. |
| Default data refresh rate is 5 seconds | The application currently has the default data refresh rate of 5 seconds for each dashboard gadget |
| Font colors and sizes of gadget titles cannot be changed | You cannot change the font size and color of the gadget titles. Only the font color of the message text can be changed in the Text Message gadgets. |
| Statistics get refreshed when the Master node is shifted from one node to the subscriber node | All the realtime stats are refreshed and the count starts from zero whenever the master node is shifted to a new Master. |
| Data Service attribute tooltips are not translated | The tooltips displayed for each data service attribute are not translated automatically. This is shown in the same language in which it was mentioned within the data service. |
| The translation is only for the left to right languages | The application supports language translation for all languages mentioned on the Languages Support page. You can place the translation file in the /root/wallboard/docker/translation folder with the name translation_code.json. The frontend should be restarted after placing the translation file in the translation folder. |
Manage space
Manage content
Integrations