Release Note

Contents

Introduction

This release note applies to all 8.5 releases of Genesys Pulse Collector.

• 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 Guide.
• 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 on 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

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

• Pulse Collector now has an ability to run an embedded version of Genesys DB Server. When running an embedded DB Server, Pulse Collector does not require a separate Database (DB) Server instance in order to connect to the Pulse DB. You can enable an embedded DB Server in Pulse Collector using the following option:

  [collector] Section
  dbthread
  Change takes effect: After restart
  Valid values: yes, no
  Default value: no
  Enables or disables running of embedded DB Server in Pulse Collector internal thread.

  Software Requirements Changes

  When running Embedded DB Server, Pulse Collector uses Genesys DB Clients which require the DBMS clients to be installed. Follow the instructions under the "DBMS Environment Settings" chapter of Genesys DB Server User Guide to install and configure those clients. Note that you probably already have necessary clients installed if all of the following is true:

  • You are upgrading Pulse Collector from an earlier release.
  • You had the Genesys DB Server installed on the host with Pulse Collector.
  • The Genesys DB Server and Pulse Collector are of the same architecture (32 or 64-bit).

  Application Configuration Changes

  If you are running Pulse Collector with Embedded DB Server after an upgrade from an earlier version, you can either perform all of the following steps to modify the configuration or just the first one and leave the configuration unchanged:

  1. Stop DB Server.
  2. Clear the DB Server field of Database Access Point application object used by Pulse Collector.
  3. Uninstall DB Server and delete its application object.

  You are not required to configure a separate DB Server application for new installations of Pulse Collector running an Embedded DB Server. The value of the DB Server field on General tab of Database Access Point application object that is used by Pulse Collector should be set to None.

  New Configuration Options

  The embedded DB Server produces its own log messages. To control what goes to the log and where the log should be written add log-db section to Collector Application options and fill it with all the options that usually go to the log section of Genesys DB Server application. If there will be no log-db section specified in Collector Application options, the logging of embedded DB Server will be controlled by options found in log section except for the following:

  1. The value for verbose option is set to standard.
  2. The log is written to the file specified in log section, but with -db suffix added.

  Limitations

  The Linux version of Pulse Collector using an embedded DB Server is unable to connect to MS SQL Server database.

• Pulse Collector now uses a unified format for the custom log messages:

  TIMESTAMP SEVERITY_LEVEL THREAD_ID Message text

  New configuration option to control log level for the custom log messages.

  [log] Section
  collector-log-level
  Changes take effect: Immediately
  Valid values: Debug, Trace, Info, Warning, Error, Fatal (case insensitive)
  Default Value: Info
  Defines log level for the custom Pulse Collector log messages. Messages with severity below this level will not be logged.
  Message severity levels:
  

  • Debug—detailed debug messages.
  • Trace—detailed informational and progress messages.
  • Info—brief informational and progress messages.
  • Warning—indicates minor recoverable errors or situations.
  • Error—indicates more severe, but recoverable errors.
  • Fatal—indicates severe, unrecoverable errors.
  • Message which stand for informational messages that appear regardless to current log level.

  Note: Log output of earlier Collector releases corresponds to the current Trace log level.

Corrections and Modifications

There are no corrections or modifications for this release.

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following correction and modification:

Genesys Pulse Collector no longer leaks memory when processing Group By statistics. (WBRT-7746)

Top of Page

Supported Operating Systems

New in This Release

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

• Support of the Group By feature of StatServer, release 8.5.103 or higher.

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector provides a new option that allows you to specify user data keys that must be excluded during the extraction of reason codes.

[scripting-variables]
Option: excluded-reason-code-keys
Valid Values: Comma separated list of user data keys
Default Value: site
Changes Take Effect: After restart

Specifies user data keys that must be excluded from the list of codes retrieved through the function G.GetReasonCodes() and from those provided by all statistics of category CurrentStateReasons.

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This version was first released as a Hot Fix on 04/15/16. This release contains the following new features or functionality:

• Genesys Pulse Collector can now optimize incoming traffic by pausing notifications from a backup Stat Server (requires Stat Server 8.5.102 or later). This feature is automatically activated and is governed by a new configuration option, suspend-notifications-from-secondary-server:

  Section: statistic-request-handling
  Option: suspend-notifications-from-secondary-server
  Valid Values: yes, no
  Default Value: yes
  Changes Take Effect: After Restart
  This option controls whether Collector should attempt to use Stat Server's capability to quickly suspend and resume notifications for all requests, when data from a particular Stat Server is not being used to generate snapshots.

• Genesys Pulse Collector supports new value, "BackupInCME", for the option statistic-request-handling/data-source-choice-strategy. When this value is specified, Genesys Pulse Collector evaluates its Stat Server choice for layout data to a Stat Server configured as primary backup in Configuration Database. However, if this Stat Server is not available, Collector attempts to use another available Stat Server instead.

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer quits unexpectedly when multiple layouts request current state statistics for the same objects. (WBRT-6974)

If you use a Stat Server release lower than 8.1.200.21, Genesys Pulse Collector now opens new statistics if you have an incorrect object type in a statistic type based on the CurrentStateReasons category. (WBRT-2908, WBRT-2904, WBRT-2903)

Top of Page

Supported Operating Systems

New in This Release

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

• The Genesys Pulse Collector cluster allocation algorithm is now updated. See details in the "Deploy Genesys Pulse Cluster Configuration" section of the Genesys Pulse Deployment Guide.

• Genesys Pulse Collector now supports the ability to specify an object name used only within Genesys Pulse that is different than the actual object name in the Configuration Server. When this is configured you can see the custom object name in Genesys Pulse widgets, although you still see the original object name when choosing objects for your widget in Genesys Pulse.

  This is the most useful for Virtual Queues when their Display Name is used in strategies, but does not work well in Genesys Pulse.

  To configure a custom Genesys Pulse object name for Configuration Server object:

  1. Set the Object's Annex option named display_name, placed in the [Genesys Pulse] section for one or many objects.
  2. Configure Collector to use custom Genesys Pulse Object Name by configuring object name format with format string %CustomName%.

  The Object Name format is configured in Genesys Pulse Collector options section [object-name-format].

  If custom name is not defined, this format specifier uses the value of the %ObjectName% specifier.

  Special case: For the Campaign Calling List (an assignment of a Calling List to a Campaign rather than a native Configuration Server object), the custom name is a combination of the custom names of the corresponding Calling List and Campaign name. If some part of this composite name is not defined, this format specifier uses the value of the %ObjectName% specifier of the respective object.

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer closes unexpectedly when multiple virtual agent groups provide information about the same agent. (WBRT-6720)

The snapshot cleanup tool no longer fails to clean up snapshots on the Windows platform. (WBRT-6690)

Genesys Pulse Collector now correctly connects to Message Server. (WBRT-6676)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

Collector now generates an error message in snapshots when formulas fail with Out of Memory (snapshot error codes 957, 958). Previously, if a formula caused large memory consumption, Collector exited. (WBRT-5933)

Genesys Pulse Collector now correctly processes adding an Agent and includes the Agent in snapshots for a Virtual Agent Group (VAG) if you change VAG membership using the following method:

1. Remove an agent from a VAG (for example, by changing Agent skills).
2. Add the same agent back to the VAG within a very short period of time.

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following correction and modification:

Collector no longer exits unexpectedly while producing data for widgets created from the standard Agent Login template, in scenarios when Stat Server is connected to the both SIP Server and Interaction Server and agents have both voice and multimedia statuses. (WBRT-6125)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer exits unexpectedly when it is stopped immediately after it starts. (WBRT-5941)

Genesys Pulse Collector no longer exits unexpectedly during script evaluation when a script assigns a native object to a local variable and attempts to access the properties or methods through that variable. (WBRT-5909)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer exits unexpectedly after a skill is removed from an Agent when multiple snapshot-building threads are enabled. (WBRT-5774)

Top of Page

Supported Operating Systems

New in This Release

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

• Genesys Pulse Collector now supports secure connections to other Genesys components: Configuration Server, DB Server, Stat Server and Message Server.

  Important: Secure connections with Message Server require an additional configuration step. You must set the field Transport Options under Advanced in the Message Server connection properties with the value tls=1.

  Warning: Use Genesys Administrator instead of the Configuration Manager to set this option, because each time you use Configuration Manager to edit the application, this setting is reset and must be renewed explicitly.

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer exits unexpectedly when you close Genesys Pulse at the same time that the reconnection to Stat Server is scheduled. (WBRT-5473)

Genesys Pulse Collector now supports transport options from the legacy [transport-gpb-out] section.

Note: Use [transport-file] section for new installations. (WBRT-5423)

Genesys Pulse Collector now includes bundled sets of options in configuration files (minimal and full) located in the subfolder extras. The default application template corresponds to the minimal file. (WBRT-5417)

Genesys Pulse Collector can now function using only the default application options.

Note: You must still configure log options to enable logging. (WBRT-5416)

Genesys Pulse Collector performance is now improved due to more granular locking. (WBRT-5405)

The Genesys Pulse Snapshot file size is now reduced by eliminating some unnecessary data fields. (WBRT-5394)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Note: This version was first released as a Hot Fix on 05/14/15.

Corrections and Modifications

This release includes the following corrections and modifications:

Both Genesys Pulse Collector and GAX must be installed on the same host. Genesys does not support deploying components of Genesys Pulse onto different hosts and using shared folders for transferring snapshots. If you use Genesys Pulse Collector Cluster configuration, you must configure the WebDav server to share the snapshot across nodes. (WBRT-5438)

Genesys Pulse Collector no longer exits unexpectedly when all the options are removed from the Collector application in configuration while Collector is still running. (WBRT-5391)

Genesys Pulse Collector no longer hangs when you stop it through SCS or by using Ctrl+C. (WBRT-5377)

Genesys Pulse Collector now correctly requests statistics of CurrentState, CurrentTargetState, and CurrentStateReasons categories. (WBRT-5328)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector now connects to the correct port of the DB Server if a non-default port is specified in the connection. (WBRT-5287)

Genesys Pulse Collector now connects to the correct port of the Message Server if a non-default port is specified in the connection. (WBRT-5286)

Genesys Pulse Collector now logs the correct port of the Stat Server if a non-default port was specified in the connection. (WBRT-5284)

You can now configure Collector to use a local Stat Server as its preferred data source (for example, co-located on the same host with Collector). To do so, you must set option statistic-request-handling/data-source-choice-strategy to value Local. (WBRT-5212)

The default value of the option stat-data-processing-thread-max-load-factor in the parallel-processing section is changed to 300. Previously, it was set to 1. (WBRT-5172)

Genesys Pulse Collector now attempts to choose only Stat Server data sources to which it has a live connection. (WBRT-5164)

The Genesys Pulse Collector application template now contains the external-heartbeat-url and external-heartbeat-folder options in the [heartbeat] section. Previously, they were incorrectly named heartbeat-external-url and heartbeat-external-folder. (WBRT-5161)

The maximum value of the option stat-data-processing-thread-max-load-factor in the parallel-processing section is now increased to 10000. (WBRT-5059)

Genesys Pulse Collector provides a new option that allows you to limit the size of the internal incoming statistic data queue to prevent out-of-memory situations.

Section: statistic-request-handling
Option: max-stat-data-queue-size
Valid Values: 1...2147483647
Default Value: 2147483647
Changes Take Effect: After restart
Limits the internal Genesys Pulse Collector statistical data queue, which stores unprocessed data from Stat Server. Incoming data, that causes this limit exceeded, will be dropped. Genesys recommends to set value of this option to an at least six times the possible maximum total number of statistics.

(WBRT-5053)

Genesys Pulse Collector provides new options that enables you can now generate compressed snapshot files, which take less disk space.

Section: transport-file
Option: compression-method
Valid Values: None, LZ4 (case-insensitive)
Default Value: None
Changes Take Effect: After Restart
Specifies whether compression should be used and which type of compression to use for the snapshot files.

Section: transport-file
Option: lz4-compression-level
Valid Values: 1...16
Default Value: 1
Changes Take Effect: After Restart
Specifies the compression level for the LZ4 compression method.

(WBRT-4548)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

The G.GetConnID(), G.GetANI() and G.GetDNIS() JavaScript functions provided within the bundled script library file gts.js, now work correctly. (WBRT-5107, WBRT-5008)

Attached data for media types other than voice are now available in Genesys Pulse Collector. Previously in some releases, they were unavailable. (WBRT-5084)

The warning about an exceeded limit of objects from the layout snapshots is no longer displayed when the object count is below the limit. Previously, the warning continued to appear after the limit was exceeded for the first time, even when the object count went back below limit. (WBRT-4950, WBRT-4924)

Genesys Pulse Collector now appropriately removes agents from layouts based on the virtual agent groups. Previously, for releases 8.5.010.xx or later, when the virtual agent group was included in more than one widget, Collector might fail to remove an agent from the virtual agent group when the agent no longer satisfied the virtual agent group condition. (WBRT-4940)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

Collector now works properly with Stat Server 8.1.0. Previously, the statistic that uses the CurrentState category (the ExtendedCurrentStatus stat type supplied with Genesys Pulse) resulted in an error. This issue affects the Current Status statistic in the Agent Login out-of-box template. (WBRT-4356)

When you use Virtual Agent Groups (VAG) with the LoggedIn expression in the Script Agent Group property in the widget, Collector no longer leaks memory as Agents log in and log out. (WBRT-3742)

Genesys Pulse Collector now uses RabbitMQ to improve the speed of updates.

The configuration option section transport-gpb-out is now named transport-file.

This release eliminates the configuration options collector/output-transport and transport-gpb-out/transport-type.

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector now supports the Agent State Reason in formulas as follows:

If Agent Status is LoggedIn, LoggedOut, AfterCallWork, NotReadyForNextCall, or WaitForNextCall, then:

• For voice, find all Agent voice DNActions where Action=AgentStatus and return all data associated with these actions as the resulting Voice Reason.

• For non-voice DNs, find DNActions where Action=AgentStatus and return the value associated with key "ReasonCode" as the resulting Multi-Media Reason.

Resulting Voice and MM Reason are concatenated using a ; separator and returned as combined Reason. (WBRT-5152)

Attached user data for non-voice media types is now available. (WBRT-5084)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

Genesys Pulse Collector no longer hangs if you stop it (for example, using kill <pid> or kill -15 <pid> commands) while it opens statistics for many layouts (which typically happens during initialization). (WBRT-5046)

Genesys Pulse Collector now correctly requests CurrentState statistics on the 32-bit Stat Server for Linux. (WBRT-5038)

The snapshot-log-level and collector-snapshot-log-level configuration options in the [output] section have three new valid values, which allow you to filter messages:

• Fatal—filter all messages below fatal (ERROR and lower)
• Unknown—filter all messages below Unknown level (FATAL and lower)
• None—filter all messages

The valid values are now: Debug, Info, Warning, Error, Fatal, Unknown, None (case-insensitive).

(WBRT-4995)

Genesys Pulse Collector now appropriately removes agents from layouts based on the virtual agent groups. Previously, for earlier 8.5.000.xx releases, when the virtual agent group was included in more than one widget, Collector might fail to remove an agent from the virtual agent group when the agent no longer satisfied the virtual agent group condition. (WBRT-4940)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Collector application metadata template file (Collector.xml) is now updated, so it can be parsed correctly during import. (WBRT-4372)

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 release of Genesys Pulse Collector.

• The following changes are made to configuration options:

  • Removed the [layout-history], [parallel-processing], [thresholds], and [transport-gpb-history] sections.
  • In the [collector] section:
  • Removed the history-transport option.
  • In the [configuration-monitoring] section:
  • Added the excluded-objects-propagation-delay and remove-dynamic-object-delay options.
  • Removed the auto-detect-dynamic-metagroups, enable-differential-layout-recheck, recheck-active-layout-definition, and strict-tenant-security options.
  • In the [layout-validation] section:
  • Renamed the enable-strict-tenant-security-validation-rule option to validate-strict-tenant-security.
  • In the [limits] section:
  • Removed the max-custom-actions-per-layout, max-custom-thresholds-per-layout, and max-threshold-associations-per-layout options.
  • In the [output] section:
  • Added the collector-snapshot-log-level and snapshot-log-level options.
  • Removed the cleanup-output option.
  • In the [scripting] section:
  • Added the stop-compute-formula-threshold-for-snapshot option.
  • Removed the cumulative-formula-script-execution-timeout, cumulative-threshold-script-execution-timeout, enable-extended-statistic-value, post-processing-script-execution-timeout, and threshold-script-execution-timeout options.
  • In the [statistics-request-handling] section:
  • Removed the optimize-statistic-requests options.
  • In the [transport-gpb-out] section:
  • Added the output-file-mode option.
  • Removed the backend-file-ext, cleanup-file-modification-age-threshold, generate-layout-info-file, and output-format options.

Corrections and Modifications

This release includes the following corrections and modifications:

When the reconnection timeout configuration option of the Configuration Server application object is set to 0 (zero), Genesys Pulse Collector now successfully reverts the reconnection timeout to the default value (10 seconds). (WBRT-3220)

Genesys Pulse Collector can now process layouts that include Campaign Groups based on Place Groups. (WBRT-3207)

Genesys Pulse Collector no longer leaks memory upon rechecking a layout configuration. (WBRT-2561, WBRT-1479)

Top of Page

Known Issues and Recommendations

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

Pulse Collector may keep updating heartbeat file when DBMS is down and collector-db is added to heartbeat- success-condition option in the [heartbeat] section.

Workaround: Add db-poller to the option value. (WBRT-8241)

Oracle 12 clients are not supported.

Workaround: If you are using Oracle 12c database with Pulse Collector, make sure that you install Oracle 11.2 client on the host that runs Collector. (WBRT-8153)

When you use a GroupBy expression that involves user data that is changed during a call, that call is counted in the group with the old value (or no value) AND in the group with the new value. You might see the Total Number of Calls without GroupBy that is less than the value of the sum of all numbers from all Groups in GroupBy. This is expected behavior from StatServer.

Workaround: Add filters to the statistic to filter out all the calls that do not have user data.

For example given GroupBy enabled stat type:

[GroupBy1]
Category=TotalNumber
GroupBy=GetString(UserData,"UserData1")
GroupByColumns=UserData1
MainMask=CallInbound
Objects=Agent
Subject=DNAction

You can add a filter like the following:

{code}
UserData1=PairExists("UserData1","*")
{code}

This filters calls until they have UserData1 attached, which prevents double counting each call with the N/A userdata (no userdata) and the UserData1 user data key. (WBRT-7702)

Widgets may display N/A values immediately after startup of Pulse Collector or a switchover of StatServers for at least one widget refresh period, when notification pausing from the backup StatServer is enabled and the StatServer supports this feature. (WBRT-7670)

If you have a multi-language Configuration Server, you must add the option -cs_codepage 65001 to the command line of Genesys Pulse Collector on the Windows platform. You may need to edit the Genesys Pulse Collector service command line in the Windows registry. (WBRT-7026)

Genesys Pulse Collector might not stop immediately when it is waiting for a response from DB Server, but does stop normally when the database request timeout expires (the default database request timeout is 180 seconds). (WBRT-6691)

Genesys Pulse Collector might incorrectly process adding an Agent and not include the Agent in snapshots for a Virtual Agent Group (VAG) if you change VAG membership using the following method:

1. Remove an agent from a VAG (for example, by changing Agent skills).
2. Add the same agent back to the VAG within very short period of time.

Workaround: To avoid this issue, set the value of the Collector remove-dynamic-object-delay option in the configuration-monitoring section to 0. (WBRT-5786)

Genesys Pulse Collector might exit unexpectedly if the volume containing the Genesys Pulse Collector log files contains insufficient disk space.

Workaround: Set up automated log management for archiving and removal. (WBRT-5484)

When Collector cannot connect to the Genesys Pulse database, attempts to stop Collector may not succeed until expiration of the database query timeout, which is configured in the DAP. If you need to terminate Collector process in this state use kill -9 on Linux. (WBRT-5356)

Important: The following applies to all Genesys Pulse Collector releases:

Red Hat Enterprise Linux (RHEL) 6.6 and CentOS 6.6 kernels 2.6.32-504.* before version kernel-2.6.32-504.16.2.el6 and RHEL 7 and CentOS 7 kernels before version kernel-3.10.0-229.7.2.el7 have a critical issue that may lead programs running on the OS to freeze. To avoid such issues, especially, in the mission-critical production environments, you must update the Linux kernel:

• for RHEL 6.6 and CentOS 6.6 at least to the version kernel-2.6.32-504.16.2.el6
• for RHEL 7 and CentOS 7 at least to the version kernel-3.10.0-229.7.2.el7

More information about the issue and this solution can be obtained at the following links:

• https://bugs.centos.org/view.php?id=8371
• https://bugzilla.redhat.com/show_bug.cgi?id=1208633
• https://access.redhat.com/solutions/1386323
• https://rhn.redhat.com/errata/RHSA-2015-0864.html
• https://rhn.redhat.com/errata/RHSA-2015-1137.html

Note: A valid Red Hat account is required to access some of the pages above. (WBRT-5579)

The Genesys Pulse Collector application template contains incorrect options:

• heartbeat/heartbeat-external-url
• heartbeat/heartbeat-external-folder

These options should be corrected to:

• heartbeat/external-heartbeat-url
• heartbeat/external-heartbeat-folder

Genesys Pulse Collector does not support State Reason for agents who use multimedia. (WBRT-5152)

A warning about exceeding the limit of objects may not disappear from layout snapshots, even if the object count falls back below the limit. (WBRT-4950, WBRT-4924)

Object status duration may be computed incorrectly, if Collector and Stat Server are running on the different hosts with non-synchronized system times. In order to achieve correct value, the system time on the Collector and Stat Server hosts need to be synchronized, then both Collector and Stat Server must be restarted. (WBRT-4926)

Genesys Pulse Collector cannot start on Red Hat Enterprise Linux release 5.5. (WBRT-4571)

When using Stat Server releases prior to 8.1.200.x, statistics that use the CurrentState category results in an error (the ExtendedCurrentStatus stat type is provided with Genesys Pulse). This affects the Current Status statistic in the Genesys-provided Agent Login template. Workaround: Use Stat Server 8.1.200.xx on Windows or 64-bit Stat Server 8.1.200.xx on Linux. (WBRT-4356)

When a connection to Stat Server is unavailable, Genesys Pulse may display incorrect values, such as 1.#IND, for some formula-based statistics, instead of ERROR or n/a. (WBRT-3560)

When the reconnection timeout configuration option of the Configuration Server application object is set to 0 (zero), Genesys Pulse Collector does not revert the reconnection timeout to the default value (10 seconds). (WBRT-3220)

Genesys Pulse Collector cannot process layouts that include Campaign Groups based on Place Groups. (WBRT-3207)

If you use Virtual Agent Groups (VAG) with LoggedIn expression in the Script Agent Group property in a widget, Genesys Pulse Collector might leak memory when Agents log in or out of Genesys Pulse. (WBRT-3742)

If you use a Stat Server release lower than 8.1.200.21, Genesys Pulse Collector might not open new statistics, if you have incorrect object type in a statistic type based on the CurrentStateReasons category. Review your custom statistic types in order to confirm you use only appropriate object types and upgrade Stat Server to release 8.1.200.21 or higher. (WBRT-2908, WBRT-2904, WBRT-2903)

For statistics that are defined as formulas, Genesys Pulse might display the values NaN or IND.xx when a formula is based on a statistic with a value of Error or N/A or if the Stat Server is unavailable. (WBRT-2702)

Genesys Pulse Collector may leak small amounts of memory upon rechecking the configuration of a layout, which should not impact performance. If you experience unusually high memory consumption, restart Genesys Pulse Collector to resolve the issue. (WBRT-2561, WBRT-1479)

If you attempt to open a layout that issues too many statistical requests (where the number of objects times the number of statistics taxes system memory), Genesys Pulse Collector will exit with either of the following error messages:

Signal SIGABRT received (Unix)
Abnormal program termination (Microsoft Windows)

Note that the total amount of memory available on the host where Genesys Pulse Collector runs must be able to simultaneously process statistical requests from all layouts. A typical statistical request requires approximately 0.8–1.3KB of memory depending on the platform. (ER# 321195063)

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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

Windows 32-bit

Windows Server 2003

Red Hat Enterprise Linux 5

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

• The Genesys Pulse 8.5 Deployment Guide helps you deploy Genesys Pulse.

• The Genesys Pulse 8.5 User's Guide is available by clicking help within the Genesys Pulse interface.

• The Genesys Administrator Extension 8.5 Deployment Guide helps you deploy Genesys Administrator Extension.

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.

Top of Page