Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|---|
8.1.200.50 [03/07/16] – Hot Fix | X | X | |||||
8.1.200.49 [02/19/16] – Hot Fix | X | X | |||||
8.1.200.48 [10/30/15] – Hot Fix | X | X | |||||
8.1.200.47 [10/09/15] – Hot Fix | X | X | |||||
8.1.200.45 [07/31/15] – Hot Fix | X | X | |||||
8.1.200.44 [06/30/15] – Hot Fix | X | X | |||||
8.1.200.43 [06/08/15] – Hot Fix | X | X | |||||
8.1.200.41 [03/20/15] – Hot Fix | X | X | |||||
8.1.200.39 [12/29/14] – Hot Fix | X | X | |||||
8.1.200.38 [11/24/14] – General | X | X | |||||
8.1.200.30 [08/21/14] – General | X | X | |||||
8.1.200.25 [07/11/14] – General | X | X | |||||
8.1.101.40 [02/14/14] – Hot Fix | X | X | |||||
8.1.101.39 [12/10/13] – General | X | X | |||||
8.1.101.36 [11/08/13] – General | X | X | |||||
8.1.101.32 [08/08/13] – General | X | X | |||||
8.1.101.29 [06/07/13] – General | X | X | |||||
8.1.100.21 [01/25/13] – General | X | X |
This release note applies to all 8.1 releases of Genesys Web Engagement Frontend.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
The Co-browse JavaScript application (part of the genesys.min.js
script) now provides a setDocumentDomain
option. If you want
to prevent modifications to the document.domain
object, you
must set this option to false
.
(WM-6612)
The Chat JavaScript application in the GPE package now properly exposes
onSession
events to configuration objects.
(WM-6596)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction or modification:
CometD connections are now restored successfully on IE8 and IE9 browsers after they were disrupted either by network problems or by server crashes. (WM-6543)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains the following new features or functionality:
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains the following new features or functionality:
You can now add X-Frame-Options
and
X-Content-Type-Options
headers to responses that come from your
Frontend and Backend servers. To do that, edit the header texts in the
<WebME root>\apps\<your app>\environment\environment.local.properties
file, then rebuild and redeploy your Web Engagement application. (WM-6274)
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains no new features or functionality:
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
Frontend Server no longer displays a list of available contexts when responding to a request that has reached the server�s root level. Previously, in addition to responding with an HTTP 404 error, Frontend Server also displayed a list of available contexts. (WM-5111)
Frontend Server correctly produces the expected number of log files
according to the time-based value of the segment option, for example,
segment=24hr
. Previously, Frontend Server processed these
values incorrectly. (WM-5956)
The last message in a chat session is now always displayed to the customer. Previously the last message in some chat sessions was not displayed to the customer. (WM-6069)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction or modification:
UserData
is now successfully passed by the integrated chat
widget to the Chat Server. (WM-5993)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains the following new features or functionality:
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This release contains the following new features or functionality:
FRONTEND_ROUTEID
with value '.' + <Frontend Server CME application name>
. For more information, see Load Balancing#Apache Sample ConfigurationsThere are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This version was first released as a Hot Fix on 11/19/14.
There are no restrictions for this release. This release contains the following new features or functionality:
This release includes the following corrections and modifications:
Genesys Web Engagement now guarantees that invitation notifications are delivered for invites that are generated as a reaction on the PageEntered event. Previously, related notifications could be lost if the CometD connection was not established when the notifications were sent. (WM-4027)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
This release includes the following corrections and modifications:
You can now specify the Chat Widget position on the screen by using the "windowSize" option. (WM-4953)
The Frontend Server log information now includes the name of the currently deployed Genesys Web Engagement application. (WM-4928, WM-4929)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
cep.domainSeparation
option in the service:cep
section on the Frontend Server application.This release includes the following corrections and modifications:
Web Engagement scripts now work if the customer's website uses the RequireJS library or any other AMD library. (WM-2715)
You can now update configuration options on the fly for the Genesys Web Engagement Frontend Server application. Previously, you had to restart the application for changes to configuration options to take effect. (WM-2158)
You can now include spaces in the Frontend Server name in Genesys Administrator. Previously, if the application name contained spaces the Frontend Server did not start. (WM-1943)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This is a hot fix for this product. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
This release includes the following corrections and modifications:
The "modal" invitation window now works correctly in Internet Explorer 7 and 8. (WM-3786)
The asynchronous SignIn
event now works correctly with and without parameters. Previously, it worked in an unstable manner when parameters were not specified. (WM-3828)
The Complex Event Processing (CEP) engine now successfully works when the Drools Rule Language (DRL) file contains the agenda-group
directive. (WM-3808)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
This release includes the following corrections and modifications:
The Frontend Server can now provide a "modal" invitation window. (WM-2884)
You can now configure the title in the window for the registration form and the callback and chat widgets. (WM-2929)
CometD initialization is now executed after the "document ready" event. Previously, it was possible for CometD to be initialized before the "document ready" event, which led to problems when the script was loaded on the page. (WM-3725)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This version was first released as a Hot Fix on 08/06/13.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
This release includes the following correction:
The localTime
parameter in the PageEntered
event is now specified in the local time. Previously, the localTime
parameter was specified in UTC. (ER# 316737658, WM-2389)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in this release of Genesys Web Engagement Frontend.
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Genesys Web Engagement Frontend.
There are no corrections or modifications for this release.
This section provides the latest information on known issues and recommendations associated with this product.
Web Engagement scripts may not work if the customer's website uses the RequireJS library or any other AMD library. (WM-2715)
Found In: 8.1.101.29 | Fixed In: 8.1.200.25 |
The Genesys Web Engagement Frontend Server application does not support updating configuration options at runtime. You must restart the Frontend Server for changes to the configuration options to take effect. (WM-2158)
Found In: 8.1.100.27 | Fixed In: 8.1.200.25 |
The application for Genesys Web Engagement Frontend Server must not have spaces in its name in Genesys Administrator. (WM-1943)
Found In: 8.1.100.27 | Fixed In: 8.1.200.25 |
The localTime
parameter in the PageEntered
event is specified in UTC instead of the local time. (ER# 316737658, WM-2389)
Found In: 8.1.100.21 | Fixed In: 8.1.101.30 |
The parameter sessionID
is absent in the events sent from the notification agent to the Frontend server. (ER# 316737651, WM-2388)
Found In: 8.1.100.21 | Fixed In: 8.1.101.30 |
The Opera Web Browser is not supported. (ER# 316065447, WM-2383)
Found In: 8.1.100.21 | Fixed In: |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see "Discontinued Support" in the Genesys Supported Operating Environment Reference Guide.
There are no discontinued items for this product.
Information in this section is included for international customers.
There are no internationalization items for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Genesys Web Engagement 8.1 Deployment Guide provides instructions for installing, configuring, starting, and stopping Genesys Web Engagement.
Genesys Web Engagement 8.1 Developer's Guide provides recommendations and code samples for customizing the out-of-the-box version of the Genesys Web Engagement.
Genesys Web Engagement 8.1 API Reference provides the REST and Javascript APIs that are available for your customization.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.