Real-Time Reporting (Genesys Pulse) Release Notes

From Genesys Documentation
Jump to: navigation, search


Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.

Important
The Release table lists the initial availability date for each release and the deployment environments for which a release is made available. Except when otherwise stated in the description for a specific release, each release includes all of the features and resolved issues that were introduced on earlier dates, regardless of the deployment environment. The features and resolved issues that apply only to a specific deployment environment are noted as such.
Available Genesys CX on Private edition Highlights Release
AWS Azure GCP
May 17, 2022

Azure.png

Security enhancements100.0.000.0015
March 24, 2022

Azure.png

PrivateEdition.png Beta Program support for Genesys Multicloud CX private edition deployments on GKE.
Important security improvements. Pulse Manage Agents support.
100.0.000.0012
December 21, 2021

Azure.png

PrivateEdition.png Important security improvements.100.0.000.0011
October 29, 2021

Azure.png

Disaster Recovery, High Availability, performance, and scaling enhancements100.0.000.0008
October 18, 2021 PrivateEdition.png Log redirection to stdout100.0.000.0006
August 19, 2021

Azure.png

PrivateEdition.png Support for arbitrary UIDs in private edition deployments on OpenShift.100.0.000.0005
July 30, 2021 AWS.png SSO support9.0.006.04
July 2, 2021 AWS.png 9.0.006.03
June 18, 2021

Azure.png

PrivateEdition.png Early Adopter Program support for Genesys Multicloud CX private edition deployments on OpenShift.9.0.100.10
March 31, 2021 AWS.png

Azure.png

Support for Genesys Engage cloud on Azure9.0.006.02

May 17, 2022Azure.png

Security Fixes

  • This release includes security fixes in the base images to remediate various non-exploitable vulnerabilities.
     (WBRT-16770)

  • Added missing HSTS headers for several Pulse API endpoints.
     (WBRT-16747)

  • Fixed permissive CORS misconfiguration.
     (WBRT-16745)

  • Removed unsecure session cookie usage.
     (WBRT-16744)

  • This release includes security fixes to remediate the non-exploitable 3rd party library vulnerabilities described in cve-2022-22965 and cve-2022-22963.
     (WBRT-16727)

Resolved Issues

  • Pulse Widgets now correctly displays object names and statistics values that contain national symbols. Previously in such scenarios, Pulse Widgets sometimes displayed empty or truncated object names and statistic values.
     (WBRT-16730)

Deprecations

  • Support for Internet Explorer 11 is discontinued. (WBRT-16828)

Known Issues

  • Pulse can import objects such as Dashboards, Wallboards and Widget Templates only into existing script folders. If the target folder does not exist, the import fails with the following error: Path does not exist. To work around this issue, ensure that the target script folder exists before you perform an import. (WBRT-16857)

March 24, 2022Azure.png PrivateEdition.png

What's New

  • Azure only: A new feature, Pulse Manage Agents, enables users with the Pulse Administrator or Pulse Manager role to perform agent management actions using Agent Widgets. This includes managing agent skills, and forcing agents to log out. For more information, see Pulse Manage Agents. (WBRT-16681)

  • Pulse now provides improved activation-pending indication for newly-created widgets. Previously, while a newly-created widgets was activating, Pulse sometimes displayed the following error: No objects. Please check widget configuration. (WBRT-16064)

Security Fixes

  • The release includes security fixes in the base images to remediate the non-exploitable vulnerability described in CVE-2022-24407. (WBRT-16584)

  • The release includes security fixes to remediate the non-exploitable 3rd party library vulnerability described in CVE-2021-36090. (WBRT-16491)

  • Cumulative upgrade of 3rd party libraries. This release includes important security fixes related to the Apache Log4j 2 vulnerability (CVE-2021-45105). (CVE-2021-44832). In particular, the Log4j library included with Pulse has been upgraded to 2.17.1. (WBRT-16398, WBRT-16549)

Resolved Issues

  • Pulse now limits the size of import files to 5MB. Previously, attempts to import larger files could fail, producing an error similar to the following: Could not connect to the server. (WBRT-16592)

  • Widgets that use the Campaign Calling List object type and selection By Group now show data as expected. (WBRT-16362)

  • On the Dashboard Management, Wallboard Management, and Widget Template Management screens, the Move function now works correctly. (WBRT-16201)

  • The overall user experience is improved in scenarios where Pulse runs in Disaster Recovery (DR) mode. (WBRT-16089)

  • Users who log in using the URL for the region that is secondary for the tenant (that is, the instance that is available only if DR is activated) are now able to successfully log out and switch to another Single Sign-On (SSO) user account. (WBRT-16066)

  • Pulse Collector no longer stops when processing layout changes at the same time as it is building the snapshot. Previously in such scenarios, when objects were selected based on agent, place, or DN group, Pulse Collector sometimes stopped. (WBRT-16444, WBRT-16356)

For private edition

  • Pulse now provides improved support for single namespace configurations, and for configurations with Virtual Private Cloud scope Domain Name System (VPC scope DNS). (WBRT-16472)

  • As of March 31, 2022, Genesys Pulse supports deployments on Google Kubernetes Engine (GKE) in Genesys Multicloud CX private edition, as part of the Beta Program (formerly referred to as EAP). (CPE-2685)

December 21, 2021Azure.png PrivateEdition.png

What's New

  • This release includes important security fixes related to the Apache Log4j 2 vulnerability (CVE-2021-44228). In particular, the Log4j library included with Genesys Pulse has been upgraded to version 2.16.0. (WBRT-16327)

Resolved Issues

  • In scenarios where a Pulse user is removed from the Configuration Server and later added back with the same user name, the user is now able to use Pulse widgets. Previously in such scenarios, the widgets loaded, but only the text No Objects appeared. (WBRT-14895)

October 29, 2021Azure.png

What's New

  • Pulse Data Collection Unit (DCU) now provides auto-scaling capabilities, which enables automatic adjustment of the number of DCU instances to accommodate changes in the number of active widgets. (WBRT-15864)

  • Pulse now serves static Pulse UI content from a content delivery network (CDN), which improves the user experience and reduces load time. To support High Availability, Pulse supports both Microsoft CDN and Verizon CDN providers. (WBRT-15759)

  • Pulse now supports Disaster Recovery (DR) in pilot light mode. This enables Pulse to start in the secondary region, and gives you read-only access to the configured dashboards of the primary region. Note that statistic values reset to 0 after failover. (WBRT-16046) (WBRT-15663)

Known Issues

  • Users who log in using the URL for the region that is secondary for the tenant (that is, the instance that is available only if DR is activated) are subsequently unable to log out and switch to another SSO user account. To work around this issue, use the WWE or Agent Setup interface log out, or clear the browser Cookies and other site data. (WBRT-16066)

  • In scenarios where a Pulse user is removed from the Configuration Server and later added back with the same user name, the user is unable to use Pulse widgets (the widgets load, but only the text "No Objects" appears).

    To work around this issue, use the Widget Management interface to remove the Pulse user account, and then re-create the user. (WBRT-14895)

  • On the Dashboard Management, Wallboard Management, and Widget Template Management screens, the Move function does not work. (WBRT-16201)

October 18, 2021PrivateEdition.png

What's New

  • Genesys Pulse now supports optional redirection of all logs to stdout (No Shared Log Volumes required). (WBRT-15921)

  • Support for deploying the Genesys Pulse service in a single namespace with other private edition services has been implemented. To enable this alternative deployment scenario, see Single namespace. (WBRT-16032)

Resolved Issues

  • Expanded widgets now load correctly.  Previously, in certain scenarios, expanded widgets failed to load. (WBRT-15971)

August 19, 2021Azure.png PrivateEdition.png

Resolved Issues

  • Widgets now appear in the expected order and size on wallboards.  Previously in some scenarios, such as when users switched between tabs, widgets sometimes unexpectedly changed order and size. (WBRT-15818)

  • Pulse configuration setting are now preserved when users log in to Pulse in more than one browser tab or session using the same credentials.  Previously in such scenarios, dashboard configuration settings were sometimes overwritten by older values. (WBRT-15792)

For private edition

  • Pulse now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.

    • The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
    • The securityContext settings exposed in the default values.yaml file specify the user and group IDs for the genesys user (500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see Configure security.
    • Pulse is expected to be deployed using the default ServiceAccount, which uses the restricted SCC. If you do not want to use arbitrary UIDs in your OpenShift deployment, you must associate the default ServiceAccount with the genesys-restricted SCC, as described in the suite-level Private Edition Guide. If you previously deployed Pulse using the default ServiceAccount associated with the genesys-restricted SCC, you must remove the association if you want OpenShift to use arbitrary UIDs. To do so, execute the following command:
      oc adm policy remove-scc-from-user genesys-restricted -z default -n <namespace> (WBRT-15873)

July 30, 2021AWS.png

Resolved Issues

  • SSO login is now enabled for tenants who have Private MPLS provisioned for Genesys Pulse. (WBRT-15017)

July 02, 2021AWS.png

Resolved Issues

  • Pulse now properly handles problems with database connections, and resumes working properly once database issues are resolved. Previously, Pulse sometimes failed to restore the database connection once issues were resolved. (WBRT-15391)

  • Users can now move Dashboard, Wallboard, and Widget Template objects between folders in Configuration Server when the [pulse]\folder_based_access option is enabled. Previously, users could move an object to another folder only if they first moved the object  to the Genesys Pulse folder. (WBRT-15352)

  • The Grid Widget now restores its size after the browser window size is restored. (WBRT-15075)

June 18, 2021Azure.png PrivateEdition.png

Resolved Issues

  • Campaign, Calling List, and Campaign Calling List objects are now correctly displayed on the widget. Previously, these objects were not displayed if users had a widget with Campaign Calling Lists selected By Group. (WBRT-15590, WBRT-14815)

  • Genesys Pulse now properly shows historical (24 hours) data on charts. (WBRT-15588, WBRT-15433)

  • Now it is possible to export Dashboards, Wallboards, and Templates saved to Configuration Server. (WBRT-15228)

Dependencies

  • With Stat Server release 8.5.112.22, Campaign statistics are visible in Genesys Pulse. (WBRT-15175, SS-9381, VOICEMCS-1515)

Known Issues

  • Dashboards, Wallboards, and Templates saved to CfgUnit/Scripts or Site/Scripts folders are exported incorrectly. (WBRT-15397)

  • Widget and Tab limits, specified for Access Groups, are not supported. (WBRT-15356)

  • Objects might not appear on a Widget immediately. It might take up to 15 minutes for new configuration objects to appear or you might see the No Objects message. (WBRT-15138, WBRT-14813)

  • The Widget Management interface does not show the actual status of a user. (WBRT-14967)

For private edition

  • Starting with this release, Genesys Pulse is available for select customers in Genesys Multicloud CX private edition, as part of the Early Adopter Program. Deployments on OpenShift Container Platform (OpenShift) are supported. (WBRT-15299)
    More info: Genesys Pulse Private Edition Guide

March 31, 2021AWS.png Azure.png

What's New

  • Starting with this release, Genesys Pulse is available in Genesys Engage cloud on Azure. (WBRT-13461)

  • The Select All checkbox is added to the Statistics tab on the widget create/edit dialog. (WBRT-12759)

  • A new widget is now located in an empty space on the right side of a dashboard. Previously, new widgets were placed in the top left position, causing a reorder of already existing widgets (WBRT-3700)

Resolved Issues

  • Widgets' locations no longer change after switching between tabs or after refreshing the page. Previously, in those scenarios, widgets' locations on the tab were rearranged. (WBRT-14173)

  • Usernames are no longer used in URL of some requests. Previously, usernames were used in API requests from Genesys Pulse User Interface, disclosing potentially sensitive information. (WBRT-12371)

Known Issues

  • Azure only. Widget and Tab limits, specified for Access Groups, are not supported. (WBRT-15356)

  • Azure only. The export of Dashboards, Wallboards, and Templates, saved to Configuration Server, does not work. (WBRT-15228)

  • Azure only. Objects might not appear on a Widget immediately. It might take up to 15 minutes for new configuration objects to appear or you might see the No Objects message. (WBRT-15138, WBRT-14813)

  • Azure only. The Widget Management interface does not show the actual status of a user. (WBRT-14967)

Prior Releases

For information about prior releases of Genesys Pulse, see Real-Time Reporting (v9).