| Line 6: | Line 6: | ||
For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the '''teamcommunicator.enable-lazy-loading''' option to <tt>true</tt> to enable a lazy loading mechanism, allowing agents to get acceptable display performance. | For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the '''teamcommunicator.enable-lazy-loading''' option to <tt>true</tt> to enable a lazy loading mechanism, allowing agents to get acceptable display performance. | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Network issues== | ==Network issues== | ||
| Line 34: | Line 30: | ||
==Workspace Performance== | ==Workspace Performance== | ||
| − | + | If you are experiencing performance issues with Workspace, you can check the browser logs for messages like the following: | |
| + | |||
| + | <nowiki>[DEBUG] [WWE.Main.Performance] [Worker] Application experiencing major performance problem (XX/60)</nowiki> | ||
| + | |||
| + | where XX is >=40 but < 50, | ||
| + | |||
| + | or: | ||
| + | |||
| + | <nowiki>[DEBUG] [WWE.Main.Performance] [Worker] Application experiencing severe performance problem (YY/60)</nowiki> | ||
| − | + | where YY is < 40. | |
| − | + | ==Native operating system call notifications== | |
| + | Sometimes agents will not have Workspace displaying in the active browser tab. Agents might be working in other applications or browser windows or the browser window containing Workspace might be minimized. In these situations, agents might miss Workspace notifications of ringing interactions. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
For Native toast usage, activation, reactivation, etc, we have information available in our wiki, that could be placed in the Premise documentation if needed. Links to information in wiki: | For Native toast usage, activation, reactivation, etc, we have information available in our wiki, that could be placed in the Premise documentation if needed. Links to information in wiki: | ||
http://internalwiki.us.int.genesyslab.com/dev_teams/index.php/Workspace_Web_Edition_-_FAQ#What_is_the_Notifications_mechanism_suggested_by_Chrome.2C_Edge_and_FireFox.3F | http://internalwiki.us.int.genesyslab.com/dev_teams/index.php/Workspace_Web_Edition_-_FAQ#What_is_the_Notifications_mechanism_suggested_by_Chrome.2C_Edge_and_FireFox.3F | ||
Revision as of 20:55, February 4, 2021
Contents
Troubleshooting Workspace Web Edition
If you are having issues with Workspace Web Edition, you can try some of these solutions.
Slow search results
For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the teamcommunicator.enable-lazy-loading option to true to enable a lazy loading mechanism, allowing agents to get acceptable display performance.
Network issues
You can review logs to determine whether agents are experiencing network issues by searching for Ajax command names followed by the time. In general, commands should take less than 1 second.
Search for "Command: '<command name>' sent in <time>"
For example: Command: 'Hold' sent in 0.337s
Website integration
Here are some troubleshooting suggestions if a website you are trying to integrate in Workspace Web Edition does not display or does not display correctly.
X-Frame-Options or Content-Security-Policy
Embedded websites might not display or might not display correctly due to X-Frame-Options or Content-Security-Policy (CSP) settings. To troubleshoot embedded website issues, review the browser logs to look for content similar to this example:
Refused to display 'https://www.mywebsite.com/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
http vs. https
Workspace only accepts https connections. If the website you are trying to integrate uses http instead you will see messages like the following in the browser logs:
Mixed Content: The page at 'https://135.39.45.252/ui/wwe/index.html?code=yPwFc1&state=3a23c01c03a51d88' was loaded over HTTPS, but requested an insecure frame 'http://www.mywebsite.com/'. This request has been blocked; the content must be served over HTTPS.
Workspace Performance
If you are experiencing performance issues with Workspace, you can check the browser logs for messages like the following:
[DEBUG] [WWE.Main.Performance] [Worker] Application experiencing major performance problem (XX/60)
where XX is >=40 but < 50,
or:
[DEBUG] [WWE.Main.Performance] [Worker] Application experiencing severe performance problem (YY/60)
where YY is < 40.
Native operating system call notifications
Sometimes agents will not have Workspace displaying in the active browser tab. Agents might be working in other applications or browser windows or the browser window containing Workspace might be minimized. In these situations, agents might miss Workspace notifications of ringing interactions.
For Native toast usage, activation, reactivation, etc, we have information available in our wiki, that could be placed in the Premise documentation if needed. Links to information in wiki: http://internalwiki.us.int.genesyslab.com/dev_teams/index.php/Workspace_Web_Edition_-_FAQ#What_is_the_Notifications_mechanism_suggested_by_Chrome.2C_Edge_and_FireFox.3F And, all the following chapters also contain useful information (why notifications doesn't appear, how to reactive notifications)