Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.210.09 [11/04/11] Hot Fix | X | X | X | X | ||
8.0.210.08 [10/25/11] Hot Fix | X | X | X | X | ||
8.0.210.07 [06/09/11] Hot Fix | X | X | X | X | ||
8.0.210.06 [04/01/11] General | X | X | X | X | ||
8.0.200.12 [01/26/11] Hot Fix | X | X | ||||
8.0.200.11 [12/17/10] General | X | X | X | X | ||
8.0.100.24 [03/11/11] Hot Fix | X | X | X | X | ||
8.0.100.20 [08/13/10] General | X | X | X | X | ||
8.0.100.18 [04/01/10] General | X | X | X | X | ||
8.0.000.16 [07/27/09] General | X | X | X | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.
This release note applies to all 8.0 releases of Interaction Server.
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
This is a hot fix release of this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
The JMS Capture Point now passes a username and password when obtaining the context of a connection. (ER# 284887461)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
If Interaction Server is configured with a Java Message Service (JMS) capture point, Interaction Server no longer consumes unbounded memory when session reconnects occur. (ER# 282851992)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
When Interaction Server starts up, it no longer generates an error message
if an iwd_jms_cp
license is not available.
Previously in this situation, Interaction Server generated a Standard level licensing violation error message,
which led to an alarm showing in Solution Control Interface.
(ER# 271001189)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
Ping
event
There are no corrections and modifications for this release of Interaction Server.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
settings
section of the Capture Point Application object:
include-ids-in-duplicate-error
Default value: false
Valid values: true, false, yes, no
Changes take effect: Upon restart
This option determines what is included in the error message that Interaction Server sends when
a CreateTask
request fails due to duplicate interaction IDs.
true,
the error message includes the actual BrokerId and CaptureId of
the existing interaction that prevented the CreateTask
request from succeeding.
false,
the error message includes the BrokerId and/or CaptureId
that are supplied in the corresponding CreateTask
request.
Note: A setting of true
has a performance impact: Interaction Server first searches for
the duplicate interaction in order to get the BrokerId and CaptureId of the existing interaction.
(ER# 264086083)
This release also includes the following corrections and modifications:
Interaction Server is now able to send Java statistics to Stat Servers that are running in backup mode as well as those running in primary mode.
Note: To receive statistics, a backup Stat Server must also satisfy all of the following requirements:
Connections
tab of the Interaction Server.
accept-clients-in-backup-mode
in its statserver
section
with a value of yes.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications:
Interaction Server no longer sends incorrect attached data to Universal Routing Server. Previously, in some rare scenarios, Interaction Server sent attached data for a previous interaction instead of the current interaction. (ER# 265226581)
Interaction Server's memory consumption no longer increases when Interaction Server is idle. (ER# 265212201)
The ParentId
field in the Rpt_Interaction
table of the Event Logger database is no longer empty. (ER# 263690697)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. There are no new features or functionality in this release.
This release also includes the following corrections and modifications:
In this release, when an agent disconnects from Interaction Server, Interaction Server takes any interactions that the agent has pulled from a workbin and returns them to that workbin. Previously, Interaction Server would return such interactions to a queue rather than a workbin. (ER# 268809327)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
Segmentation
tab in the View object of a Business Process).
Interaction Server now has the option to guarantee that interactions that have been selected by segmentation are pushed to Universal Routing Server regardless of the order defined by the view. The order is taken into account during segmentation. To enable this mode of operation, do the following:
cached_at
to the Interaction Server database
by executing one of the following statements:
alter table interactions add cached_at datetime
alter table interactions add cached_at date
alter table interactions add cached_at timestamp
honor-segmentation-generations
to the settings
section
of the Interaction Server application object and set its value to true.
The default value of this option is false
and changes to it take effect after restart.
Note: Interaction Server does not check the presence of the
cached_at
field or its type at startup.
If the honor-segmentation-generations
option is set to true
and the field is absent, the segmentation feature does not work and
there will be SQL errors in the Interaction Server log.
If the option is set to the default value false,
database modification is not necessary.
(ER# 254897090)
View
section on the Annex
tab,
create an option called default-limit
and assign it a positive integer value.
Now, instead of calculating the per segment limit dynamically based on segments that are actually present, Interaction Server will use this default segment limit. (ER# 254932316)
Note:
This release also includes the following corrections and modifications:
Now Interaction Server properly handles the situation in which a third-party-server timeout expires. If Interaction Server does not receive a response to the third-party server request from the third-party server within the timeout, Interaction Server considers this request to have failed, and sends an error message to Universal Routing Server. Previously in this situation, Interaction Server did not cancel the third-party server request and did not send an error message to Universal Routing Server. (ER# 254855403)
This release improves the processing of concurrent requests for the same interaction. The improved processing greatly reduces the occurrence of incorrect reports indicating that the interaction does not exist or is not available. However this issue may still occur under very rare circumstances with slow database access. (ER# 254072381)
In this release, Interaction Server properly handles reconnection with Universal Routing Server after a network disconnect. Previously, in some cases, Interaction Server allowed a second connection from the same client. Now Interaction Server permits a client, such as Universal Routing Server, to open a new connection only after any previous connection from that client is closed.
Note: The ADDP protocol must be enabled in connections to Interaction Server. Otherwise Interaction Server may not detect disconnections correctly. (ER# 255461905)
Interaction Server no longer exits unexpectedly if a DB Server has not been assigned on the General
tab of the Logger DAP for Interaction Server. (ER# 215418771 )
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
assigned_at
and assigned_to
.completed_at
timestamp.This release also includes the following corrections and modifications:
A new option event-filter-by-id
was added
to the event-filtering
section of the Interaction Server DAP object.
This option provides the ability to specify a comma-separated list of EventIDs
to be written to the Event Logger database.
Refer to the eServices (Multimedia) 8.0 Reference Manual for more information about this option.
(ER# 245986568)
The dbo
account does not have to be an owner of the
Interaction Server database on MS SQL. This restriction was removed for
this release of Interaction Server. (ER# 245959212)
Interaction Server is now able to distribute an EventInteractionSubmitted
when an interaction is submitted by a client application without an established client name. (ER# 245959198)
Interaction Server now correctly sets attr_ref_id=-1
for
self-generated events (events that are not responses to requests). In
previous releases, Interaction Server incorrectly set the attr_ref_id=0
for these events. (ER# 245959164)
This release corrects an issue involving the deletion of virtual
route points in a particular scenario. Previously, when a strategy was
activated using the Set Strategy State
method, Interaction
Server created corresponding virtual routing points on all switches that
belonged to the same Tenant. If the strategy was deactivated manually,
the route points were only deleted from the Multimedia Switch. The
corresponding virtual routing points were not. As a result, when
Universal Routing Server (URS) was restarted, URS received EventErrors
from T-Server stating that the DNs were not configured in Configuration Manager. (ER# 226802206)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of Interaction Server.
RequestWorkflowConfiguration, RequestWorkbinTypesInfo,
and RequestWorkbinStatistic
are now available for reporting clients and routing engine clients (the
internal routing engine client that is productized in Platform SDK
8.0).
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
This release corrects an issue that, in special circumstances, caused Interaction Server to reply to RequestChangeProperties
. with an error message of no interaction ID found. (ER# 229398326)
This release corrects an issue in the Stat Server listener that caused Interaction Server to terminate. (ER# 229398230)
This release improves handling of requests to the interactions
database on the DB2 platform. As a result, deadlocks occur less frequently. (ER# 230035922)
This release correctly handles deadlocks arising from database requests that do not initiate any explicit database transaction (such as snapshot requests without locks). Previously, this scenario caused the database channel to be disabled, and no response was sent to the client. (ER# 221039170)
The usage of properties with a decimal data type in database fields for routing segmentation is now supported when using an IBM DB2 database engine. (ER# 218576691)
This section provides the latest information on known issues and recommendations associated with this product.
Interaction Server requires an ESP port to connect to ESP (External Services Protocol) servers, such as Chat Server. Prior to release 8.0.1, Interaction Server searched for an ESP port, defined either as a configuration option or a connection, regardless of how the connection was defined in the client application configuration. Starting with the 8.0.1 release, it uses the exact connection specified in the client's configuration. So if the client is configured to use the default port, then Interaction Server uses the default port and does not attempt to use the ESP port definition in the server configuration. This means that connecting Interaction Server to an ESP server has two requirements:
Server Info
tab must define a port with ID = ESP.
(You must manually type this value for ID.)
Connections
tab must have a connection to the ESP Server
with Port ID = ESP.
(You select this value of Port ID from a drop-down list.)
For backward compatibility with Chat Server 8.0.0 and older, which uses the option esp-server-port
to
designate an ESP port, do as follows:
Server Info
tab.
Port ID = ESP
and Communication Port
duplicating
the port number specified by the esp-server-port
option.
ESP
in the Port ID
drop-down list.
The Interaction Server Database Access Point (DAP) must have its Case Conversion
attribute (on the
DB Info
tab) set to any
or upper.
Setting it to lower
causes an error when Interaction Server initializes. To avoid this problem, use version 8.0.300.00 or higher of DB Server.
The scripts for setting up and pruning the Event Logger database, which are supplied with Interaction Server, do not support MSSQL 2000.
Interaction Server fails to switchover completely after several primary/backup switches under heavy load. The status looks correct in Solution Control Interface (SCI), but Interaction Server fails to switchover. (ER# 263968187)
Found In: 8.0.200.11 | Fixed In: |
In some scenarios, on Interaction Server or DB Server switchovers,
the same XML inbound message can be processed more than once.
Interaction Server issues EventError Database error
for these interactions and rolls them back to a message queue, but at the same time it places them into the interactions
table.
Since messages still in message queue Interaction Server pulls them one
more time and submits them again. (ER# 263120407)
Found In: 8.0.200.11 | Fixed In: |
When Interaction Server connects a backup ESP server that is running in primary mode, it connects to the default port instead of the ESP port. It does this even when ESP ports are configured in both primary and backup ESP servers. (For a definition of ESP server see the "Glossary" section of the eServices (Multimedia) 8.0 User's Guide.) (ER# 256029884)
Found In: 8.0.100.20 | Fixed In: |
On the Widows platform, Interaction Server exits, generating a Dr. Watson report, after making a large number of unsuccessful attempts to connect to DB Server. In this scenario on Solaris, Interaction Server simply stops attempting to connect to DB Server. (ER# 250203203)
Found In: 8.0.100.18 | Fixed In: |
Interaction Server submits interactions to Universal Routing Server (URS) with a delay after losing and regaining its connection to DB Server. (ER# 240735125)
Found In: 8.0.100.18 | Fixed In: |
When a strategy is activated using the Set Strategy State
method, Interaction Server creates corresponding virtual routing points
on all switches that belong to the same Tenant. If the strategy is
deactivated manually, the route points are only deleted from the
Multimedia Switch. The corresponding virtual routing points are not. As a
result, when Universal Routing Server (URS) is restarted, URS will
receive EventErrors
from T-Server stating that the DNs are not configured in Configuration Manager. (ER# 226802206)
Found In: 8.0.000.16 | Fixed In: 8.0.100.18 |
In rare circumstances on UNIX, when Interaction Server is stopped from Solution Control Interface while under load, Interaction Server will exit with a core dump. (ER# 217483826)
Found In: 7.6.101.15 | Fixed In: 8.0.100.18 |
Interaction Server may exit unexpectedly if a DB Server has not been assigned on the General
tab of the Logger DAP for Interaction Server. (ER# 215418771)
Found In: 7.6.101.15 | Fixed In: 8.0.100.20 |
It is not possible to lock a snapshot with more than 1000 interactions in Oracle. The Interaction Server option max-interactions-per-snapshot
has a maximum value of 2000
, but Oracle has a limitation of 1000
. If using an Oracle database, be aware of this Oracle limitation.
(ER# 204795083)
Found In: 7.6.101.15 | Fixed In: |
Interaction Server does not support the mandatory-logging
option in the logger-settings
section of the Interaction Server DAP options, described in the eServices (Multimedia) 8.0 Reference Manual. This option is reserved for future use. (ER# 195790067)
Found In: 7.6.101.15 | Fixed In: |
In rare cases under heavy loads, Interaction Server might not switch to primary mode during switchover. This problem is intermittent; it occurs if switchovers are performed simultaneously with short intervals between switchovers. (ER# 172356768)
Workaround: Restart both primary and backup Interaction Servers.
Found In: 7.6.000.15 | Fixed In: |
When the option delay‑updates
is set to true
,
and the external_id
is changed during the current handling session,
requests to get properties based on external_id
may fail if the database was not updated with the new value. (ER# 168597976)
Workaround: Use the User Data ForceDatabaseUpdate
key in RequestChangeProperties
.
Found In: 7.6.000.15 | Fixed In: |
Under heavy loads, extra interactions may be submitted to Universal Routing Server in the following situations:
(ER# 166786271)
Found In: 7.6.000.15 | Fixed In: |
In rare cases when multiple clients are manipulating the same interaction simultaneously,
the following statistics may be miscalculated: queue-current in processing, queue-current length, queue-current waiting processing,
tenant-current in processing,
and tenant-current waiting processing.
(ER# 180485806)
Found In: 7.5.000.19 | Fixed In: |
Interaction Server does not issue any warning when it sees an invalid value
for option max-submitted-interactions
(in the Annex
tab of a Strategy
object)
and max-submission-rate
(in section Interaction Server Name
of the Annex
of
Universal Routing Server). Interaction Server uses the default value zero
if the value submitted is invalid; this disables submission to Universal Routing Server.
(ER# 107154166, 107154168)
Found In: 7.5.000.10 | Fixed In: |
Setting an interaction custom property to an empty string value effectively removes this property from attached data in the interaction when Interaction Server uses Oracle database. (ER# 105650427)
Found In: 7.5.000.10 | Fixed In: |
If you update a routing strategy and save the changes before Interaction Server has finished initializing, Interaction Server exits. (ER# 57111954)
Found In: 7.2.000.10 | Fixed In: |
If Interaction Server is processing multiple interactions when it receives a command to terminate normally, it may take several minutes to fully shut down. This is because of the time it takes for Interaction Server to properly finalize all updates. (ER# 41880734)
Found In: 7.2.000.10 | Fixed In: |
Interaction Server may freeze under the following condition: If a Tenant is added/removed in the Interaction Server Application when Interaction Server has not yet finished reading the configuration of its existing Tenants. (ER# 34221195)
Workaround: Restart Interaction Server after making Tenant changes.
Found In: 7.2.000.07 | Fixed In: |
If the name of a custom property in the Interactions table contains a space character, Interaction Server does not convert the name into a standard property name. (ER# 102339)
Found In: 7.1.000.03 | Fixed In: |
In the rare situation where both Configuration Server and Interaction Server are running without a network connection between them, Interaction Server does not react to the deletion or addition of objects in Configuration Manager. (ER# 101751)
Found In: 7.1.000.03 | Fixed In: |
Interaction Server does not support interaction level logging. (ER# 74418)
Found In: 7.0.000.09 | 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.
Windows 2000 is no longer supported.
Discontinued As Of: 8.0.000.16 |
Information in this section is included for international customers.
There are no internationalization issues 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.
eServices 8.0 Deployment Guide describes deployment procedures for all eServices/Multimedia components. It also contains a high-level description of the eServices/Multimedia system, its architecture, and a list of new features in the current release.
eServices Social Media Solution Guide, available on the Genesys Documentation website, is a guide to deploying and using the social media functionality of eServices.
eServices 8.0 User's Guide provides overall information about and recommendations on the use and operation of Genesys eServices/Multimedia.
eServices 8.0 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
eServices 8.0 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple Samples, and describes procedures for customizing them.
For a listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component, see:
eServices 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
eServices 8.0 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
eServices 8.0 Knowledge Manager Help is a guide to the Knowledge Manager user interface.
Universal Routing 8.0 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for eServices/Multimedia.
Universal Routing 8.0 Business Process User's Guide contains step-by-step instructions for using Interaction Routing Designer to design interaction workflows. It also describes the sample business processes supplied with eServices/Multimedia.
Genesys Desktop 7.6 Help is a guide to using the Genesys Desktop.
Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. For authoritative description of the event messages, see the next item.
The API References of the Platform SDK, which provide the authoritative
information on methods and functions for each SDK, including requests and
events. The class Message
includes all event and request messages.
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.