Release Note

Outbound Contact Manager

7.6.x

Genesys Telecommunications Laboratories, Inc. © 2008–2011

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.6.101.13 [10/12/11] – Hot Fix           X
7.6.101.12 [04/26/10] – General           X
7.6.101.10 [12/18/09] – Hot Fix           X
7.6.101.09 [12/09/09] – General (Under Shipping Control)           X
7.6.101.07 [06/08/09] – Hot Fix           X
7.6.101.06 [04/21/09] – Hot Fix           X
7.6.101.04 [11/17/08] – Hot Fix           X
7.6.101.03 [9/26/08] – General           X
7.6.100.01 [5/12/08] – General           X
7.6.000.09 [2/15/08] – General           X

Link to 7.5 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

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.genesyslab.com for more details.

This release note applies to all 7.6 releases of Outbound Contact Manager (OCM).

Use of Third-Party Software

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 technical support representative if you have any questions.


Release Number 7.6.101.13 [10/12/11] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:


OCM now correctly detects the version of Oracle Database Management System (DBMS) when opening a calling list table in the Calling List details view. Previously, OCM was not able to correctly detect the Oracle DBMS version if the major database release number of Oracle was 10 or higher. As a result, OCM did not work efficiently with calling lists larger than 3000 records on the Oracle DBMS if the active dialing and/or viewing filter contained an ORDER BY clause. OCM also displayed a warning message stating that the read operation may require more time; the message also recommended adding more WHERE conditions to the filter. (ER# 281845479)


Top of Page


Release Number 7.6.101.12 [04/26/10] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains the following feature or functionality:

Corrections and Modifications

This release includes no corrections and modifications.

Top of Page


Release Number 7.6.101.10 [12/18/09] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix release for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


OCM now correctly supports viewing filters with conditions that include user-defined fields with the datetime type in the following scenario:

  1. The Date/Time format (short date) is set differently from the default setting for the EnUS locale. (For example, the format is set to dd-m-yyyy.)
  2. An Oracle DBMS is used for the Calling List table.
  3. A viewing filter that includes a condition for a field with the datetime type is defined using the Standard mode tab of the Edit filter dialog box.
  4. This viewing filter is applied to the Calling List in the Calling List Details View.

Previously, in this scenario, OCM constructed an invalid SQL SELECT statement.

(ER# 231705705)


Top of Page


Release Number 7.6.101.09 [12/09/09] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this 7.6 release of Outbound Contact Manager.

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Release Number 7.6.101.07 [06/08/09] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix release for this product. This release contains the following new feature or functionality:

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page


Release Number 7.6.101.06 [04/21/09] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix release for this product. This release contains the following new feature or functionality:

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page


Release Number 7.6.101.04 [11/17/08] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix release for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:


When using the Append and Update option to import a Calling List from a file to an existing Calling List, Outbound Contact Manager (OCM) now imports all records. Previously, OCM might have lost records in this scenario. (ER# 213140655)


Top of Page


Release Number 7.6.101.03 [9/26/08] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this 7.6 release of Outbound Contact Manager.

Corrections and Modifications

This release includes the following correction or modification:


OCM now correctly functions in the following scenario:

Previously, in this scenario, OCM might have terminated unexpectedly. In addition, if the Modify all action was selected, the error message Error code 80004005 Method '~' of object '~' failed was generated.

(ER# 201955252)


Top of Page


Release Number 7.6.100.01 [5/12/08] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this 7.6 release of Outbound Contact Manager.

Corrections and Modifications

This release also includes the following corrections and modifications:


OCM no longer terminates unexpectedly in the following scenario:

  1. Open the Calling List Details view.
  2. Scroll down to the last visible record in the open calling list.
  3. Select Update Record from the main menu or the context menu, or double-click that record.

Note: This problem did not occur for small Calling Lists where all records were visible in the dialog box and therefore did not require scrolling.

(ER# 181677701)


OCM displays the correct record in the Update Record dialog box in the following scenario:

  1. Open the Calling List Details view.
  2. Scroll down to a record in the open calling list.
  3. Select Update Record from the main menu or the context menu, or double-click that record.

Previously, when you selected Update Record or double-clicked a record after scrolling through the list, OCM displayed a different record in the Update Record dialog box.

Note: This problem did not occur for small Calling Lists where all records were visible in the dialog box and therefore did not require scrolling.

(ER# 181677707)


Top of Page


Release Number 7.6.000.09 [2/15/08] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Outbound Contact Manager.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:


Outbound Contact Manager (OCM) now handles correctly a Time Zone with its offset set to fractional parts of an hour (for example IST, GMT+5:30). As a result, in this release, OCM now calculates the time parameters of the campaign sequence correctly in the following scenario:

  1. Launch an instance of OCM, on one machine configured with a local Time Zone and the offset set to fractional parts of an hour.
  2. In OCM, specify values for the Start Time and Stop at time parameters of the campaign sequence.
  3. Launch another instance of OCM, on another machine also configured with a local Time Zone, but with the offset set to whole hours (for example NET, GMT+4:00).
  4. In OCM on this second machine, open or run the same campaign sequence. OCM now calculates all of the time parameters of the campaign sequence correctly.

(ER# 164704851)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


When using the Append New (no chain merge) option to import a Calling List from a file to an existing Calling List, Outbound Contact Manager (OCM) may lose records. (ER# 213446241)

Found In: 7.6.101.03 Fixed In: 

If you import or export records to or from a Calling List using the Append New (no chain merge) option, OCM does not insert all of the records from the source Calling List into the destination list when the destination list is empty. (ER# 206808631)

Found In: 7.6.101.03 Fixed In: 

When running on Windows 2000, OCM might terminate unexpectedly in the following scenario:

(ER# 195179841)

Found In: 7.6.101.03 Fixed In: 

When running on Windows 2000, OCM might terminate unexpectedly in the following scenario:

(ER# 192963260)

Found In: 7.6.101.03 Fixed In: 

When running on Windows 2000, OCM might terminate unexpectedly if a campaign sequence is updated in OCM (for example, if the Start Time sequence or Description properties are updated or a new sequence item is added to the campaign sequence). (ER# 206126241)

Found In: 7.6.101.03 Fixed In: 

If you are importing records from a large Calling List (for example, 25,000 records) into a small Calling List (for example, 5 records), OCM might stop functioning. (ER# 181643511)

Found In: 7.6.100.01 Fixed In: 

When you import records from another Calling List using the Append New option, if Outbound Contact Manager (OCM) encounters a record with the same values in the Calling List already, instead of skipping this record, OCM adds the record with a new chain_id. As a result, the same record is listed twice with two different chain_id values. For more information about this Append New option, see the Outbound Contact Manager Help. (ER#s 168294524, 193112163)

Found In: 7.1.000.03 Fixed In: 7.6.101.03

When using Oracle or Informix databases, OCM generates a viewing filter with incorrect syntax when filtering on the datetime field if the viewing filter was created or edited using Standard mode in the Edit filter dialog box. When this filter is required, Genesys recommends that you create it using Expert mode in the Edit filter dialog box. (ER# 84887)

Found In: 6.5.100.06 Fixed In: 

Top of Page


Discontinued Support

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: 7.6.101.12

Top of Page


Internationalization

Information in this section is included for international customers.


There are no internationalization issues for this product.


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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.

Top of Page