| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 8.0.300.04 [12/20/10] � General | X | X | X | X | ||
| 8.0.200.16 [07/27/12] � Hot Fix | X | |||||
| 8.0.200.15 [06/08/12] � Hot Fix | X | X | X | X | ||
| 8.0.200.14 [01/20/12] � Hot Fix | X | |||||
| 8.0.200.13 [11/30/11] � Hot Fix | X | |||||
| 8.0.200.12 [06/03/11] � General | X | X | X | X | ||
| 8.0.200.11 [11/19/10] � General | X | X | X | X | ||
| 8.0.200.09 [08/06/10] � General | X | X | X | X | ||
| 8.0.100.14 [09/14/10] � Hot Fix | X | X | X | X | ||
| 8.0.100.13 [03/24/10] � General | X | X | X | X | ||
| 8.0.000.12 [12/22/10] � Hot Fix | X | |||||
| 8.0.000.09 [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 Universal Contact 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
There are no restrictions for this release. This section describes new features that were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
The script
upgrade_mssql_7.1_to_7.2.sql,which upgrades MS SQL databases from 7.1 to 7.2,
now correctly upgrades the StandardResponseUsage table.
(ER# 258152401)
The synchronization algorithm has been modified to manage large amounts of merged contact data. (ER# 258502644)
Pruning and archiving operations are now based on UTC time rather than local time. (ER# 264139845)
The default configuration now supports connecting to Oracle RAC. (ER# 257255381)
In this release, when UCS switches from backup to primary mode, it first sends confirmation of the switchover, then performs synchronization of objects in the Configuration Server database after a short delay. Previously, having synchronization precede switchover confirmation sometimes caused UCS to disconnect from Local Control Agent (LCA). (ER# 263799307)
Searching for contacts has been improved. Previously, searching for contacts sometimes returned the error
getMergeDetail Map failed.
(ER# 257254882)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
Now, by default UCS does not allow the use of a wildcard as the first character in search requests in the index. Previously, starting a request with several wildcards caused UCS to become unresponsive. The new default behavior can be controlled with the following new option, which can be added to the
index.srl, index.contact, and index.interaction sections.
allow-leading-wildcard
Possible values: true, false
Default value: false
If false, a search request cannot start with a wildcard.
If true, a search request can start with a wildcard, which is the previous behavior.
In this mode, only one wildcard character is allowed.
Be sure not to start requests with multiple wildcards.
(ER# 304362110)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
UCS is no longer prevented from starting when a Configuration Server Application object is disabled in the Configuration Layer. (ER# 299726693)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
In this release, when UCS switches from backup to primary mode, it first sends confirmation of the switchover, then performs synchronization of objects in the Configuration Server database after a short delay. Previously, having synchronization precede switchover confirmation sometimes caused UCS to disconnect from Local Control Agent (LCA). (ER# 290909887)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
UCS generates ID codes for various purposes, such as identifying contacts, interactions, and attachments. In the relatively rare case that two or more UCS instances are started within the same second, they may generate identical IDs, and this can cause issues when the UCS instances are connected to the same Interaction Server.
IDs are generated using several parts, including one called Ordinal, which is incremented at each restart of UCS. To avoid the possibility of identical IDs, this release introduces the following option, in the
settings section:
id-generation-ordinal
Default value: 0 (zero)
Valid values: positive integer or dbid
Changes take effect: Upon restart
Effects of the possible values:
dbid�Ordinal is reset to the database ID number of the UCS Application object.
0 (zero), no value, or invalid value�Previous behavior: Ordinal is incremented upon restart.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
The first query in the sequence for creating a Training Object now correctly selects all required interactions. For this correction to take effect properly, you must also upgrade Knowledge Manager to version 8.0.210.03 or later. (ER# 270847024)
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 Universal Contact Server.
This release includes the following corrections and modifications:
While UCS is loading its configuration cache, if it loses its connection to Configuration Server or Configuration Server Proxy, it now attempts to reconnect until the connection is re-established. Previously in this scenario, UCS would not reconnect unless it was restarted. (ER# 260144581, 260127419)
UCS is now able to switch from backup to primary when reporting is disabled. Previously, it would fail with a null pointer exception. (ER# 260437941, 260437949)
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 Universal Contact Server. New features listed under two headings: Context Services (known as Context Management Services in release 8.0.1) and Classic UCS (all UCS capabilities and features other than those grouped under Context Services).
This release also includes the following corrections and modifications:
This release corrects an issue that caused UCS to use up all connections in the database connection pool.
Previously, using incorrect parameters when calling FindOrCreate on the service PhoneCallService would
prevent
the underlying database connection from being freed.
Repeating this error several times could consume all database
connections which would prevent UCS from executing further queries.
Now database connections are correctly freed even if the parameters are
incorrect.
(ER# 256304367)
This release corrects two issues with Long values on Oracle, described here and here in this Release Note. (ER# 246550251, 243869333)
Previously, the format of dates in the full text search index was yyyy.mm.dd.hh.ss.S, where hours used a 12-hour format.
This prevented searches from distinguishing AM and PM times.
Now dates use the ISO8601 format yyyy-MM-dd'T'HH:mm:ss.SSS'Z' and the Time Zone is now set to GMT.
An example date is 2009-08-05T11:31:53.000Z.
Note: Client applications must also use the new format, remembering to escape the colon character ( : ).
For example, a search for the above date must be formatted like this: 2009-08-05T11\:31\:53.000Z.
(ER# 249726727)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
This release no longer fails when parsing the dates of incoming chat interactions.
Previously, the create, update, and close requests sometimes failed when parsing dates under high traffic conditions.
(ER# 253620101)
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 Universal Contact Server.
This release also includes the following corrections and modifications:
UCS no longer fails to start on some Windows systems due to the absence of the msvcr71.dll file.
That file is now included in ContactServiceStarter.exe.
(ER# 229440004)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Universal Contact Server.
This release includes the following corrections and modifications:
Pruning and archiving operations are now based on UTC time rather than local time. (ER# 264086238)
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 Universal Contact Server.
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
The update method of the Open Media Interaction service no longer has any limitations and works with any type of interaction. (ER# 217020411)
Detailed schema information has been added to log message 21103. (ER# 217097561)
By default since the 7.2 release of the product, a custom ServerFactory was used
instead of the Sun ServerFactory for RMI communications. In order to increase performance
and benefits from the new JDK 1.6 improvements, the default behavior in the 8.0 release will
be to use the Sun ServerFactory. This change affects clients that used duplex mode to overcome
restrictive firewall limitations between UCS and its UCSAPI client applications
(Interaction SDK, Genesys Agent Desktop, E-mail Server Java, etc.).
Now, in order to use this feature the following option must be added in the settings section
of the UCS application:
ucsapi-custom-socket=true
Note: Duplex mode still must be enabled by using the following option
in the settings section of the UCS application:
ucsapi-duplex-mode=true.
(ER# 220621711)
A ThreadID is generated for new transactions that do not have a ThreadID or ParentID to provide to the
InsertInteraction request. (ER# 227816634)
Through Platform SDK, the ability to retrieve the category/standard response tree without details. (ER# 228127643)
This section provides the latest information on known issues and recommendations associated with this product.
Note: Known Issues that are relevant only to the Context Management Services/Context Services functionality are prefaced with (CMS) or (CS).
The following information is missing from the eServices 8.0 Reference Manual and the Universal Contact Server 8.0 Context Services User's Guide:
To connect UCS to an Oracle Real Application Cluster (RAC), configure a DAP for UCS as follows:
settings containing
the following options:
[ServerInfo]
host: rac1
ports: default, 1521
[Options > settings]
ONSConfiguration: nodes=rac1:6251,rac2:6251,rac3:6251
host1: rac2
port1: 1521
host2: rac3
port2: 1521
| Found In: 8.0.300.04 | Fixed In: |
Starting with the 8.0.3 release, UCS needs additional configuration to
be able to connect to Oracle using SID instead of Database Name:
Add the property ‑Ducp=false to the [JavaArgs] section
of the ContactServerDriver.ini file in both primary and backup UCS installation folders.
Note, however, that using the Database Name is the prefered method.
(ER# 265341781)
| Found In: 8.0.300.04 | Fixed In: |
When an archiving or pruning task is scheduled, UCS starts archiving at the correct date and time, but does not notify UCS Manager about the progress of the task. Therefore UCS Manager does not display correct information about the progress of the task. This problem also exists with UCS 8.0.2x. (ER# 265164801)
| Found In: 8.0.300.04 | Fixed In: |
(CS) Contact Services does not return attributes with the null value, but does return attributes whose value is "" (empty string). When setting an attribute's value to "" (empty string), MS SQL stores it as is, but Oracle stores Null instead. This has the consequence of changing the behavior of the system when querying these attributes. Consider a profile with FirstName = Jean-Luc, LastName = Picard, and Surname = "".
When connected to an MS SQL Server database, Context Services returns this profile:
"FirstName": "Jean-Luc",
"LastName": "Picard",
"Surname": ""
"FirstName": "Jean-Luc",
"LastName": "Picard",
As a workaround, insert " " (space character) instead of "" (empty string) to prevent Oracle from substituting Null. When reading values the extra character must be removed. To store a space character, you must add a second space character, and remove it when reading the data back. (ER# 256795031)
| Found In: 8.0.200.09 | Fixed In: |
An issue occurs when UCS runs in a virtual environment, on Windows Server 2008, connected to an MS SQL database under a very high load. Under these conditions, UCS may exit with the message
OutOfMemoryError: unable to create new native thread,
although there is still free memory and the thread count is less than 50. There are two possible workarounds:
ContactServerDriver.ini file,
located at the root of your UCS installation, by adding -Xss128K to the [JavaArgs] section.
ContactServerDriver.ini file,
located at the root of your UCS installation, by adding -Djdbc4=false in the [JavaArgs] section.
| Found In: 8.0.200.09 | Fixed In: |
The default UCS configuration does not support connecting to Oracle RAC: UCS does not set RAC-specific options for the new Oracle driver. To enable UCS to connect to Oracle RAC, the previous iNet Seropto driver must be used. To do this,
ContactServerDriver.ini file,
located at the root of your UCS installation, by adding -Djdbc4=false to the [JavaArgs] section.
| Found In: 8.0.200.09 | Fixed In: 8.0.300.04 |
(CS) When creating, updating, or deleting a contact (customer) using Context Services, the full text search index of UCS is not updated. A workaround is to rebuild the contact index manually. (ER# 255033111)
| Found In: 8.0.200.09 | Fixed In: |
(CS) Some configuration options are not present in the UCS template. They are
cview section, the options related to configuring SSL: keyPassword,
keystorePassword, keystorePath, keystoreType, port-http, and port-https.
business-attributes section along with its map-names option.
| Found In: 8.0.200.09 | Fixed In: |
UCS is not able to archive an interaction if a single document is attached to the interaction multiple times (that is, if more than one attachment of this interaction points to the same document). To enable UCS to archive such an interaction, extra attachments must be manually deleted using a desktop application or an SQL query. (ER# 247801651)
| Found In: 8.0.100.13 | Fixed In: |
(CMS) It is possible to complete a service, state, or task operation without having started it first. (This is because for performance reasons the
complete operation does not check if any corresponding start operation has been executed.)
Completing an unstarted service/state/task can result in unexpected behavior, such as:
| Found In: 8.0.100.13 | Fixed In: |
(CMS)
When creating an extension with a Double attribute type on an MS-SQL 2005 RDBMS,
it is not possible to store the Java constant Double.MIN_VALUE.
As a workaround, use a bigger value.
Note that Double.MIN_VALUE is 0.0000...049, where the number of zeroes is 324.
(ER# 241113933)
| Found In: 8.0.100.13 | Fixed In: |
| Found In: 8.0.100.13 | Fixed In: 8.0.200.09 |
(CMS)
When creating an extension with a Double attribute type on an Oracle RDBMS, there are the following limitations:
Double.MAX_VALUE 1.7976931348623157 E+308 because Oracle
only supports 1.79769313486231 E+308 (notice the two missing digits at the end).
Double.MIN_VALUE 2.2250738585072014 E-308 because
Oracle only supports 2.22507485850720 E-308 (notice the two missing digits at the end).
| Found In: 8.0.100.13 | Fixed In: |
UCS running on the Windows or Solaris platform does not support a DB2 database on the AIX platform. With DB2 on the AIX platform, UCS must also be on AIX. (ER# 244195442)
| Found In: 8.0.100.13 | Fixed In: |
(CMS)
On an Oracle RDBMS it is not possible to store long values larger than 9999999999999998 or
less than -9999999999999998.
Inserting values ouside of this range would result in a loss of precision
(for example, 9999999999999999 will be inserted as 10000000000000000).
This issue has two consequences:
long type in profile extensions cannot hold such values.
long , once the 9999999999999999th service is started,
behavior may be unpredictable.
| Found In: 8.0.100.13 | Fixed In: 8.0.200.09 |
For performance reasons, pruning the Main database queries does not process indexed documents.
Workaround: If indexed search service is enabled and pruning on the Main database is necessary:
(ER# 227161222)
| Found In: 8.0.000.09 | Fixed In: |
UCS cannot start on some Windows systems if the msvcr71.dll file is absent.
Workaround: Add the msvcr71.dll file to the UCS directory.
(ER# 229440004)
| Found In: 8.0.000.09 | Fixed In: 8.0.100.13 |
During the indexing process of the EmailAddress field of a Contact document,
all the characters in the field are changed to lowercase and the @ - _ < > ' " characters are removed.
During the search process the same procedure is performed to remove these characters from the search
criteria since they are no longer present in the database record.
Due to a limitation of a 3rd party library, this process is not performed automatically if a special
character is present in query string (* ~ ?).
As a result, a search using any of these characters (@ - _ < > ' " ) as criteria
will return no results.
Workaround: Replace these characters by the space character in the query string.
(ER# 230058221)
| Found In: 8.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.09 |
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 components. It also contains a high-level description of the eServices 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.
eServices 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
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 7.6 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 7.6 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.