9.0.002.16
Genesys Co-browse Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 11/19/18 | Hot Fix | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Co-browse now synchronizes dynamically deleted CSS nodes (<style> and <link rel="stylesheet">). Previously, if such a node was deleted during a Co-browse session, this was not synchronized, and in some cases it led to differences in how the page was displayed to the end user and to the agent.
Resolved Issues
This release contains the following resolved issues:
Co-browse now works correctly if the Co-browse server URL includes query parameters. For example, if your instrumentation points to https://example.com/cobrowse?access_token=7NNXLq3SH9KtRiMMuB9akLGzSG50J4Un, this now works correctly. Previously Co-browse did not support any query parameters in the URL. (CB-5881)
Co-browse now correctly synchronizes pages that use <link rel="import"> tags. (CB-5877)
Co-browse no longer synchronizes most of the <meta> tags. Previously, their synchronization could negatively affect the experience in certain scenarios. (CB-5870)
Co-browse now sends the correct notification when signaling about the session end. Previously, Co-browse was not sending the proper reason, which affected the JavaScript APIs, and the agent UI where a wrong notification was shown when the session ended. (CB-5851)
Invalid selectors in the DOM restrictions configuration are now ignored, and the co-browse session can start. Also, information about invalid selectors are logged in the end-user browser console (you must set debug: true in the instrumentation). Previously, Co-browse was unable to start a session if there was an invalid selector in the DOM restrictions configuration. (CB-5850)
The customer-facing tooltip indicating masked content from the agent is now removed when the co-browse session ends. (CB-5415)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.002.16.