Jump to: navigation, search

Known Issues and Recommendations

Voice Platform Reporting Server

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Voice Platform Reporting Server. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.


See also Internationalization Issues.



There are duplicates in the tenant-id parameter value of the VAR Actions report response when the user generates the VAR IVR Actions reports by using the Reporting Server Web Service API. Example:

tenant-id= 1.1.1.1.1.1.1.1.1.1.104.104.104.104.104.104.104.104.104.104.104.104.104.104.104.
1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.104.104.

The tenant-id parameter value, which is an optional value, should be the hierarchy of tenants that will be received, for example, x.y.z.

In this example, the value should be: tenant-id=1.104 OR tenant-id=104

Note: There are no issues in reports that are shown in Genesys Administrator / GAX UI.

ID: GVP-23146 Found In: 8.5.130.78 Fixed In: 

Certain Reporting Server retention policies are required to be above a minimum value; however, the Data Retention Policy Wizard does not currently support the enforcement of these restrictions. Consequently, if a retention policy value is set below the minimum, the Reporting Server ignores this value and uses the minimum value instead. All of the daily, weekly, and monthly retention policies have a minimum retention requirement of 31 days, and all retention policies must have a duration of at least 1 day. ()

ID: ER# 246766671 Found In: 8.1.202.28 Fixed In: 

When querying for call log events through the Reporting Server web services, if you specify the from parameter, you must also specify the to parameter.

ID: ER# 191736736 Found In: 8.0.004.46 Fixed In: 

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 invalid. The correct URL to refer the Valid Values for those configuration options is http://www.quartz-scheduler.org/api/2.2.1/org/quartz/CronExpression.html

ID: GVP-23796 Found In: 8.0.004.46 Fixed In: 8.5.181.77

For MSML related calls, there is no latency support for media service calls types such as conference and record because there are no prompt metrics for this type of calls. This is as designed.

ID: GVP-23541 Found In: 8.5.130.61 Fixed In: 

The IP ReadMe for this component states incorrectly that GVP 8.5.0 supports 32-bit RHEL 6. The IP ReadMe will be corrected to remove this incorrect information in a future release.


A minor change is required when Reporting Server is deployed with an Oracle RAC database. When the hibernate.remote.database configuration option is configured, the Reporting Server internally appends some parameters to the value of the hibernate.remote.url option, including the value of the hibernate.remote.database option. Therefore, to ensure the hibernate.remote.url option is properly configured for use with Oracle RAC, ensure the following appropriate action is taken, based on the Reporting Server release you are using:

  • Reporting Server 8.1.4 release: Configure the hibernate.remote.database option with the value blank.
  • Reporting Server 8.1.3 and earlier releases: Delete the hibernate.remote.database configuration option.
ID: GVP-18143 Found In: 8.1.410.00 Fixed In: 


Internationalization Issues

Information in this section is included for international customers.


There are no internationalization issues for this product.


Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 15, 2017, at 08:48.