9.0.000.07
Genesys Co-browse Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 03/02/18 | General | 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 supports Windows Server 2016.
- Co-browse now supports Citrix XenDesktop v7.6 and Citrix XenApp v7.8.
- Co-browse now has improved logging in case of Cassandra connection issues.
- Co-browse Server now adds a Date header to its REST API responses in accordance with RFC 2616.
- The Session ID is now displayed in a format that is easier to read, minimizing errors when the end-user must read it to an agent over a voice connection.
- The CORS policy is now stricter. By default, the allowed origins are left empty and are no longer set to “all origins allowed (“*”)“. You must configure the allowed origins during deployment:
- [cross-origin] allowedOrigins
- [http-proxy] allowedExternalDomains
- The configuration property setDocumentDomain in the JavaScript Configuration API is now set to false by default. This means that Co-browse no longer sets the document.domain property of the page, which resolves some potential compatibility issues with your scripts. However, this also means that co-browsing for subdomain iframes is not supported by default. To enable co-browsing of subdomain iframes, set setDocumentDomain to true in your instrumentation.
- Co-browse Server no longer starts if you haven't specified a value for the mandatory [cluster] url configuration option.
- genesys.min.js (pre-integrated Co-browse, Chat, and Web Engagement JavaScript clients) is now deprecated. You must now use Genesys Widgets and gcb.min.js for your website instrumentation. genesys.min.js and all other embeddable JavaScript files other than gcb.min.js will be removed in future releases.
Resolved Issues
This release contains the following resolved issues:
This release includes important security updates. (CB-4834)
The maxOfflineDuration and disableWebSockets configuration options must now be set from the cobrowse section in the instrumentation (for example, _genesys.cobrowse.maxOfflineDuration). Setting these options from outside of this section is now deprecated (for example, do not set _genesys.maxOfflineDuration). (CB-4990)
Callback-polling (JSONP-based) transport was discontinued. Co-browse JavaScript clients now connect to Co-browse Server using either WebSockets or Ajax long-polling. There are still some JSONP-based requests to Co-browse Server, but it is no longer supported for general communication during a Co-browse session.
We highly recommend that you configure your infrastructure to enable WebSockets support, as it provides smoother user experience and reduces the load on the clients, the infrastructure, and the Co-browse Server. (CB-4900)
The History REST API is now deprecated and will be discontinued in a future release. (CB-4833)
Co-browse now has a more reliable synchronization of <select> and other input elements in case they're recreated in DOM with a new value (as opposed to just being assigned a new value). This improves support for some JavaScript frameworks, such as ReactJS. (CB-4826)
Co-browse dependencies have been updated to improve performance and address potential issues. (CB-4821)
Co-browse now has improved stability on the pages that contain iframes when an agent is using Workspace Desktop Edition or Workspace Web Edition via Internet Explorer. (CB-4721)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.000.07.