Release Note

Contents

Introduction

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).

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

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.

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

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:

• As of August 2010, the release type for OCM 7.6.101.12 was changed from Hot Fix to General.

• As of August 2010, OCM supports the Windows 7 operating system.

• OCM now includes a new Append all option among the Calling List import and export operations. When you select the radio button for this option, OCM imports/exports all records from or to a Calling List (or a file when importing). All records from the origination list are imported/exported with a new unique chain_id value and the unmodified chain_n value, while the existing records in the destination list remain unchanged. OCM ensures that the chain structure from the origination list is maintained in the destination list. Previously, OCM did not support the Append all option. (ER# 249365134)

Corrections and Modifications

This release includes no corrections and modifications.

Top of Page

Supported Operating Systems

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

Supported Operating Systems

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.

• OCM now supports the Progressive GVP dialing mode, introduced in Outbound Contact 8.0. For more information about this dialing mode, see the Outbound Contact 8.0 Deployment Guide.

• OCM now supports the Instant Messaging contact info type in addition to the other contact info types that are currently supported.

• The OCM installation package includes an OC_Manager_761.xml file. This is a template file that can be used with Genesys Administrator 8.0.2 to import metadata with all of OCM's configuration options.

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

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

• OCM now includes a new option, as described below:

  rej-file-path
  Type: Optional
  Default Value: . (the current directory)
  Valid Values: Any valid path to the directory where *.rej files will be stored
  Changes Take Effect: Immediately

  Specifies the storage location path to the log files (<calling list name>*.rej) that are created when records are imported or exported. If the option is set to a period (.), the default value, or to an empty string, the files are stored in the same directory as the OCM executable. You can specify either an absolute or a relative path to the directory. The option value should include the path to the directory but not the log file name. The user must also have write permissions to the specified directory.

  You define this option in the OCManager section, on the Options tab of the OCM Application object.

  Two option value examples include:

  • rej-file-path = C:\RejFiles\
  • rej-file-path = ..\RejFiles\

  (ER# 227666877)

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

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

• OCM now stores the definition of the viewing filters for each user in the OCManager_<user name> section (Annex tab) of the Calling List configuration object. This enables OCM users (those with distinct user names when logging into OCM) to have their own viewing filters when working simultaneously on the same calling list. Previously, OCM only allowed one viewing filter for each calling list, and that viewing filter applied to all users who worked with the same list. (ER# 222635343)

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page

Supported Operating Systems

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

Supported Operating Systems

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.

• OCM can now run on the Windows Vista operating system.

• A new Append New (no chain merge) option was added to the Calling List import and export operations. When the radio button for this option is selected, OCM ensures that chains are not merged in the destination Calling List when the chain_id value of the record(s) in the source and destination lists is the same. OCM prevents the appending of existing records with the same chain_id value to the destination chain by assigning a unique chain_id value to them, but retaining the chain_n value to avoid a scenario where chains of different records from different Calling Lists are mixed.

  For example, if you select this option and your existing Calling List includes a record with chain_id=1 and chain_n=0, and you import a chain of records that includes three records with chain_id=1 and chain_n=0, chain_n=1, and chain_n=2 respectively, the first record from the chain of three records from the imported Calling List will be dropped as a duplicate record and the other two records will be appended to the destination list with a new chain_id value while retaining their respective chain_n values. In contrast, if you select the Append New option, when you import the records, the record with chain_id=1 and chain_n=0 from the imported Calling List will still be dropped, but the other records with the same chain_id=1 setting and different chain_n values will be imported and merged with the existing records with chain_id=1.

  Note: The Append New (no chain merge) option is not documented in the Outbound Contact Manager 7.6 Help.

Corrections and Modifications

This release includes the following correction or modification:

OCM now correctly functions in the following scenario:

• In the Calling List configuration, the default value for either the daily_from or daily_till fields is set to a value of 86400 or greater.
• The user selects the Insert record action in the Calling List Details view.

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

Supported Operating Systems

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.

• OCM now supports the 9.1 version of IBM DB2 DBMS (Database Management System).

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

Supported Operating Systems

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.

• Outbound Contact Manager (OCM) can now be configured to timeout and lock the application window after periods of inactivity, then require the user to log in again, in order to provide greater security.
• OCM can display a security banner on user login to meet corporate security standards that require notification and acceptance of certain terms when accessing corporate applications.
• OCM now allows importing chains of records from one Calling List to another, when the databases are different. Previously, both calling lists had to be in the same format, using the same DBMS type, and located in the same database.

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)

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)

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

• OCM is connected to Configuration Server release 7.5.
• A Campaign Group object, that belongs to a Tenant that is currently active within OCM, is modified in the configuration.

(ER# 195179841)

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

• A user logs in to OCM.
• The user selects a Campaign Group in the Campaigns view.
• The user minimizes the OCM window and leaves it minimized for some time (several hours).

(ER# 192963260)

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)

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)

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)

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)

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.

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.

• The Outbound Contact 7.6 Deployment Guide provides architectural information, instructions on how to install and configure Outbound Contact 7.6 components, configuration option descriptions, and other related information.

• The Outbound Contact 7.6 Reference Manual describes application features for Outbound Contact 7.6 and provides information about constants, communication protocols, and other information.

• The Outbound Contact Manager 7.6 Help file describes how to use Outbound Contact Manager.

• The Framework 7.6 Combined Log Events Help file describes log event messages for all Genesys server products.

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