8.5.101.02
Genesys Co-browse Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 06/27/17 | General | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
-
Genesys Co-browse now supports the following browsers for tablets and smartphones:
- Google Chrome on Android (tested with Chrome 58)
- Safari 9 and above on IOS
-
The default value of the browserHardCacheDuration option is now 0. Now, Co-browse will not use hard caching by default. Static files and other files will be checked for relevance before they are picked from the cache.
Previously, the default value was 1800 for 30 minutes of hard cache.
In cases without backward compatibility for Co-browse server and client interactions, using hard cached files without checking for relevance could lead to errors until Co-browse receives the newest versions of the client-side files. Co-browse server receives new file versions in a time period no longer than specified in the browserHardCacheDuration option.
- Co-browse now synchronizes additional events when an agent is in Write Mode:
- focus and blur for <input> and <textarea> elements
- mousedown and mouseup for all elements except <select> which is excluded due to an iOS bug
- mouseenter and mouseleave
- Co-browse changed its algorithm for synchronizing :hover CSS effects. Previously, Co-browse added a CSS class to elements under a user's or agent's mouse cursor. This class interfered with the CSS of some websites in cases with CSS selectors like element[class=value]. Now instead of adding a CSS class, Co-browse adds an attribute to elements.
The Co-browse widget's style is now aligned with the Genesys Widgets default dark theme. You can switch to the previous style by adding the following to your website instrumentation:
... cobrowse: { theme: 'old-yellow' ...
If your website contains functionality bound to these events, it will now successfully trigger during a Co-browse session.
Resolved Issues
This release contains the following resolved issues:
When the localization configuration option was set, agents were sometimes not able to join a Co-browse session on the first attempt. Agents can now join Co-browse sessions on the first attempt. (CB-4343)
When creating a session, Co-browse now waits 15 seconds before telling a user the session could not be started because of a timeout. Previously, the value for this timeout was five seconds which was not enough on slower mobile networks. (CB-4251)
Co-browse sessions no longer end for non-critical exceptions. (CB-4250)
Co-browse no longer sets the JSESSIONID cookie. (CB-4216)
When the url option in the cluster section uses HTTPS, the BAYEUX_BROWSER cookie is now set with the Secure flag. Note that this cookie is set only when not using WebSockets. (CB-4215)
Co-browse now synchronizes CSS with more stability in cases where a stylesheet contains syntax errors.
Features such as :hover synchronization, may still not work for stylesheets with errors, but resources referenced in the stylesheet like images or fonts will always correctly load on the agent side. (CB-4187)
Improved CSS synchronization stability for CSS files with incorrect content types.. (CB-4150)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.101.02.