Jump to: navigation, search

Genesys Co-browse Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
07/08/16 General X X X

Helpful Links

Releases Info

Product Documentation

Genesys Co-browse

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • This version is compatible with Workspace Desktop Edition plugin version
  • You can now prohibit your agents from handling more than one co-browsing session at the same time. For more information, see Genesys Co-browse Plug-in for Workspace Desktop Edition Release Notes
  • Co-browse now enforces event ordering when synchronizing DOM changes. In general, this leads to increased stability, especially on highly dynamic pages, such as pages with JavaScript-based animation.
  • Co-browse data now remains in Cassandra for 1 day (24 hours) by default. Previously, the retention policy was 14 days.
  • Co-browse now automatically adds necessary cross-origin HTTP headers for proxied fonts. You do not need to specifically configure headers for your fonts to make them accessible for agents during Co-browsing.
  • Increased the log level of messages that disable Message Server alarms from INFO to WARN.
  • DOM Control is now automatically enforced for all children elements of a configured parent element.
  • Co-browse now automatically re-synchronizes the current page if it detects a synchronization abnormality. By automatically re-synchronizing, Co-browse improves synchronization of pages that use web technologies in unexpected or erroneous ways.
  • mouseup events now execute along with click events when an agent clicks their mouse in Write Mode. mouseup events fire when a pointing device is released over an element. Executing mouseup events along with click events accommodates web pages where functionality is bound to mouseup events instead of click events.
  • Co-browse now successfully works around a bug in the MutationObserver API of Internet Explorer. In certain cases, this bug led to errors in text synchronization when using Internet Explorer.
  • Co-browse now silently ignores more types of errors in your CSS files. For best stability, we still recommend fixing all CSS errors.
    You can check your CSS files for errors using freely available tools such as http://csslint.net
  • Co-browse now uses CQL queries to work with Cassandra instead of the deprecated Thrift protocol. Starting with this release, you no longer need to set the start_rpc option to true in the external Cassandra configuration.
  • Workspace Web Edition no longer triggers an inactivity timeout when an agent is busy in a co-browsing session. Note that HTCC should be version or above.
  • Updated the OWASP Zed Attack Proxy shipped with Co-browse from version 2.3.1 to version 2.4.3.

Resolved Issues

This release contains the following resolved issues:

Fixed issue where radio buttons with square bracket symbols in the name attribute sometimes incorrectly rendered on the agent side. (CB-3672)

Context menu (right-click) is now disabled in the Co-browsing area for agents. This prevents agents from occasionally navigating to another page and losing the Co-browse session. (CB-3617)

Fixed issues with the View Load event for custom Workspace Desktop Edition plug-ins when the Co-browse plug-in is also installed. (CB-3599)

Added additional protection from "man-in-the-middle" attacks to prevent JavaScript injections from executing in the agent desktop plugin. (CB-3598)

In agreement with best practices for security, Co-browse now customizes all error pages and does not disclose any information about the underlying platform. (CB-3573)

A web page containing a link element with no rel attribute no longer breaks Co-browsing. (CB-3544)

Fixed issues with newer versions of Chrome sometimes causing lag in scrolling synchronization. (CB-3539)

Fixed issue where marked checkboxes sometimes rendered as unchecked on the agent side. (CB-3521)

Improved CSS synchronization stability. (CB-3513)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on March 2, 2018, at 19:00.
Comments or questions about this documentation? Contact us for support!