Jump to: navigation, search

Genesys Pulse Collector Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
02/29/16 General X X

Helpful Links

What's New

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

Resolved Issues

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)

Upon a layout configuration update, Genesys Pulse Collector no longer opens statistic requests mistakenly for the individual objects. These requests are excluded from the layout snapshot because they exceed the layout object number limit. (WBRT-6684)

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

Genesys Pulse Collector no longer closes unexpectedly when there are multiple layouts created for similar Stat Server virtual agent groups. (WBRT-6644)

Upgrade Notes

Refer to the Deployment Procedure for this release to deploy the installation package within your environment.

Supported Languages

See Release 8.5.1 Translation Support.

This page was last edited on May 12, 2017, at 18:43.
Comments or questions about this documentation? Contact us for support!