Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.401.06 [03/07/14] – General | X | X | ||||
8.1.400.19 [01/15/14] – Hotfix | X | X | ||||
8.1.400.17 [12/09/13] – Hotfix | X | X | ||||
8.1.400.09 [10/31/13] – General (Under Shipping Control) | X | X |
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.
This release note applies to all 8.1 releases of Pulse Collector.
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
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Pulse Collector.
EZPulse Collector is renamed Pulse Collector. See the Pulse 8.1 Deployment Guide for additional details.
The following changes are made to configuration options:
metagroup-contents-recheck-delay
configuration option in
the [configuration-monitoring
] is added.3-3600
for the heartbeat-period
option in the [heartbeat
] section from the Collector application.15
for the
cleanup-file-modification-age-threshold
configuration option in the
[transport-*
] sectioncollector.js
value is added to the default values for the
js-modules
configuration option in [scripting
] section.ezpulse-file-ext
configuration option in the [transport-*
]
section is renamed backend-file-ext
.Pulse Collector now supports UNC paths as location of the output files on the Windows platform.
This release includes the following corrections and modifications:
When a user removes statistics that caused errors, Pulse Collector now correctly removes the related error messages from the widgets. Previously, the error messages might have remained in the widget. (WBRT-3144)
After changing the objects in a widget, Pulse Collector no longer causes unpredictable memory usage growth while checking the configuration. (WBRT-3120)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
Pulse Collector now successfully opens statistics after new statistic types are added to Stat Server while Pulse Collector was running. (WBRT-3045)
For Pulse widgets created using the Agent Login
template, Pulse now displays empty values for the Extension
and Position
fields for logged-out agents. Previously in this scenario, Pulse incorrectly displayed (N/A)
. (WBRT-2970)
Pulse now displays the correct value Error
for a formula-based statistic that contains a JavaScript syntax error in the formula definition. Previously in this scenario, Pulse incorrectly displayed n/a
. (WBRT-2963)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that were introduced in this release of Pulse Collector.
metagroup-contents-recheck-delay
configuration option in the configuration-monitoring
section. It helps optimize performance of Pulse Collector during changes, such as adding or removing configuration objects in the configuration object groups, such as Agent Groups, Place Groups, or DN Groups.
This release includes the following corrections and modifications:
If you use Microsoft SQL Server as your relational DBMS for Pulse and your DB Server runs on the 64-bit Windows, layouts are now successfully activated.
Previously, because of incorrect handling of the column type VARBINARY(MAX)
in the DBServer, Pulse Collector logged error messages.
(WBRT-2747)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release is under shipping control. This section describes new features that were introduced in this release of Pulse Collector.
Note: This component was previously available as a restricted release.
This release includes the following corrections and modifications:
Pulse Collector now correctly represents the SwitchDBID
property of the ObjectDN
script object. Previously, Pulse Collector incorrectly represented it as the SwitchID
property.
(WBRT-2255, WBRT-2252)
Pulse Collector now correctly represents the Agents
property of the GroupCurrentState
script object.
Previously, Pulse Collector incorrectly represented it as GroupID
property.
(WBRT-2254)
You can now successfully use statistics of the SCurrentStateReasons
category for an object of
type Agent Group
. Previously in this scenario, Pulse Collector might fail.
(WBRT-2253)
This section provides the latest information on known issues and recommendations associated with this product.
When the reconnection timeout configuration option of the Configuration Server application
object
is set to 0
(zero), Pulse Collector does not revert the reconnection timeout to
the default value (10 seconds).
(WBRT-3220)
Found In: 8.1.401.06 | Fixed In: |
Pulse Collector cannot process layouts that include Campaign Groups based on Place Groups. (WBRT-3207)
Found In: 8.1.401.06 | Fixed In: |
Pulse incorrectly displays n/a
instead of Error
when the JavaScript-based custom formula statistic definition contains a syntax error. (WBRT-2963)
Found In: 8.1.400.17 | Fixed In: 8.1.400.19 |
If you use a Stat Server release lower than 8.1.200.21, 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)
Found In: 8.1.400.17 | Fixed In: |
For statistics that are defined as formulas, 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)
Found In: 8.1.400.17 | Fixed In: |
If you use Microsoft SQL Server as your RDBMS for Pulse and your DB Server runs on the x64 Windows,
layouts are not activated due to incorrect handling of the column type VARBINARY(MAX)
in the DBServer
and Pulse Collector logs error messages similar to the following:
2013-10-29 12:01:10.715 (6580) Collector: Error: Schedule(274700): Invalid GPB definition! 2013-10-29 12:01:10.718 (6580) Collector: Error: Schedule object for Schedule(274700) was not created.
To avoid this issue, modify the pulse_init_mssql.sql
script to replace VARBINARY(MAX)
with IMAGE
column type for the WBRT_LAYOUT
table
creation. The edited script fragment should be similar to the following:
create table WBRT_LAYOUT ( LAYOUT_KEY integer not null , USCN bigint not null , LAYOUT_STATUS integer not null , APPLICATION_KEY integer not null , TENANT_ID integer not null , LAYOUT_NAME varchar(255) not null , LAYOUT_DESC varchar(255) , BODY_HASH_1 bigint , BODY_HASH_2 bigint , LAYOUT_BODY image , REQUESTED_STATUS integer not null , constraint PK_WBRT_LAYOUT_LAYOUT_KEY primary key (LAYOUT_KEY) ) go
(WBRT-2747)
Found In: 8.1.400.09 | Fixed In: 8.1.400.17 |
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 Pulse Collector to resolve the issue. (WBRT-2561, WBRT-1479)
Found In: 8.1.400.09 | Fixed In: |
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), 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 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)
Found In: 8.1.400.09 | Fixed In: |
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.
There are no discontinued features or functionality for this product.
Information in this section is included for international customers.
There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Genesys Customer Care website. The following documentation also contains information about this software.
The Pulse 8.1 Deployment Guide, which helps you deploy Pulse.
The Pulse 8.1 Help file, available by clicking help
within the Pulse interface.
The Framework 8.1 Genesys Administrator Extension Deployment Guide, which helps you deploy Genesys Administrator Extension.
Product documentation is provided on the Genesys 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.