Voice Platform Reporting Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Supports Red Hat Enterprise Linux 7.0. See the Supported Operating Environment: Genesys Voice Platform page for more detailed information and a list of all supported operating systems.
- Supports JRE Version 8. See the Supported Operating Environment: Genesys Voice Platform page for more detailed information and a list of all supported operating systems.
- Supports connections to SQL Server AlwaysOn Availability Groups for SQL Server 2012, 2014, and 2016.
- Supports TLS 1.2 connection to Resource Manager, Media Control Platform, and secure HTTP interfaces.
- Supports an updated JDBC driver for SQL Server to version 6.0.
- The Reporting Server landing page now displays the new Genesys logo.
This release contains the following resolved issues:
When calls for a specific time period do not have an ivr_action_XXXX event, Reporting Server now returns the response There is no VAR IVR action data that matches your query, while generating the VAR IVR Actions report. Previously in this situation, RS threw a generic exception. (GVP-23430)
Reporting Server can now be configured to add the X-Frame-Options: DENY HTTP header and value in Web API responses to defend against Clickjacking. Previously, Reporting Server had no remediation against Clickjacking vulnerability. (GVP-24041)
The Cron scheduling reference URL in the Valid Values field for some of the configuration options in the [schedule] section of Reporting Server XML file is no longer invalid. The correct URL to refer to in the Valid Values field for those configuration options has been added: http://www.quartz-scheduler.org (GVP-23796)
The valid value database is now spelled correctly in the Reporting Server rs.storage.metricsfilter configuration option. Previously, it was misspelled databse. (GVP-23429)
The parameter page-size, when applied to the SQA Failures Web Service, is no longer ignored if the value is greater than 100. This parameter works correctly with other GVP Web services. Previously, it was ignored when applied to the SQA Failures Web Service. (GVP-23427)
Reporting Server now generates the VAR Action report in comparatively less time (5 to 10 minutes) and with less CPU consumption. Previously, Reporting Server took more time (1 or more hours) and consumed more CPU, depending on the amount of VAR CDRs data that it processed. (GVP-23426)
Reporting Server no longer fails to process incoming data because of a DB error - force roll-back. java.util.ConcurrentModificationException. (GVP-23425)
When Reporting Server is configured to work with redundant, high-availability Configuration Servers (CS_Primary and CS_Backup), two or more switchovers between Configuration Servers no longer causes Reporting Server to lose its connection to the primary Configuration Server. (GVP-23424)
Reporting Server now can be configured to not time out while loading large configuration objects during initialization. Previously, Reporting Server could throw the exception Timeout waiting for server response message when a large data set had not finished loading.
Set the Reporting Server application configuration option retrieveMultipleObjectsTimeoutValue to the default value 180000 (milliseconds) to allow sufficient time to retrieve multiple objects from Configuration Server. (GVP-23423)
Reporting Server no longer displays a negative value for Duration in the VAR Action report. (GVP-23372)
Reporting Server now supports specifying the transaction isolation level when initiating a connection to Microsoft SQL Server. (GVP-23371)
Reporting Server now escapes HTML tags that might be included in Web Service API requests to prevent the Cross Site Scripting (XSS) vulnerability. (GVP-23149)