Release Advisory

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.

The following information applies to Genesys 8.1.x software and is important for you to note:

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 Customer Care representative if you have any questions.

Genesys Administrator combines the functionality of Configuration Manager, Solution Control Interface, and Outbound Contact Manager.

Note: Genesys Administrator requires Management Framework 8.0.x or later. To use Role-Based Access Control, Configuration Server 8.0.2 or later is required. To use the dialing mode Predictive GVP in Outbound Contact, Configuration Server 8.1.1 or later is required. To work in multi-language environments, Configuration Server 8.1.2 or later is required.

Genesys has identified an issue with Genesys Administrator release 8.1.306.02 and is retracting this maintenance release, effective immediately. When you try editing a configuration object of type Application, the option settings for that object are deleted. Unfortunately, there is no way to recover this lost data. However, the only impact is to edited Application objects, and all other data in the Configuration Database remains intact and unchanged.

If you have already installed release 8.1.306.02, Genesys recommends that you immediately uninstall it and upgrade to the latest General release 8.1.306.03.

The following Outbound functionalities in Genesys Administrator require Outbound 8.1.2 or later:

• Customization of counters for Calling List-related real-time reporting.
• New optimization parameters Average Distribution Time and Maximum Gain.
• Selecting statistics for Calling List-, Campaign-, and Campaign Group-related real-time reporting.

Genesys Administrator is located on the Genesys Administrator 8.1 CD.

For detailed information about the operating systems, browsers, and Database Management Systems (DBMS) supported by Genesys Administrator, see the Genesys Supported Operating Environment Reference Guide.

Notes:

• If you are installing Genesys Administrator on Windows 2008, make sure that the compatibility mode component for Microsoft IIS 7 is already installed. Refer to Microsoft documentation for details.

• .NET Framework 3.5 SP1 must be installed on the host on which Genesys Administrator 8.0.300.19 or later is running.

• If you will be using Genesys Administrator in your hierarchical multi-tenant configuration, and will be having more than 500 tenants, Genesys strongly recommends that you use Mozilla Firefox as your web browser.

• Other Applications and Solutions may support DBMS versions different from those supported by Genesys Administrator. Refer to product-specific documentation for detailed information about supported DBMS versions.

When running the Genesys Administrator setup.exe file and setting up any Localization Pack, you must initiate execution with elevated credentials. Make sure you run any of Genesys Administrator's setup files using the Windows Run as administrator functionality; refer to your Windows documentation for exact instructions.

To work with the Log Database and Outbound Calling Lists on any of the supported Database Management Systems, DB Server must be installed and configured.

To view all of the features of Genesys Administrator, you must use a minimum screen resolution of at least 1024x768, although higher resolutions are recommended. When working in 1024x768 mode, you must ensure that you have all browser windows maximized to provide a clear view of all parts of the interface.

Genesys Administrator requires at least 1 GB of disk space available.

In certain situations, if https protocol is used to communicate with Genesys Administrator, and the user is using Internet Explorer 6, 7 or 8, he or she might get the following message: This page contains both secure and non-secure items. This message is displayed because of a known issue in which a valid JavaScript directive is incorrectly interpreted by these versions of Internet Explorer.

In fact, there are no non-secure items on the page, and this message can be safely ignored. However, Genesys strongly recommends that you upgrade to Internet Explorer 9, or disable mixed content in your Internet Explorer settings to eliminate the message.

If you want to change the name of the default user from default, make sure that you first create a Role object with full access to Genesys Administrator, and then assign this role to the default user. You can then change the name of the default user at will.

For detailed descriptions of Log Events generated by Genesys components, refer to Framework 8.1 Combined Log Events Help. To access this Help file:

1. Download the file fr_logevents-help.zip to your local computer.
2. On your local machine, extract the contents of this file to a new or empty folder.
3. In this folder, open the file fr_logevents-help.chm.

You cannot edit values of configuration options that are more than 4000 characters long in Genesys Administrator. If you need to modify option values that are longer than 4000 characters, use Configuration Manager to work with these options.

To use Genesys Administrator, Genesys Voice Platform (GVP) users must be using a minimum version of GVP, as specified in the Genesys Voice Platform 8.1 Deployment Guide.

When a child tenant that has been assigned a logical resource group by its parent tenant is moved to another parent within the hierarchy, the logical resource group will remain assigned to the child tenant that was moved, breaking the hierarchical model. Before such a move is made, the logical resource group should be manually unassigned from the child tenant.

Do not change the name of a Campaign if that Campaign has Campaign Groups associated with it. Doing so might prevent Stat Server from providing the correct statistics for each affected dialing session.

Top of Page