Interaction Recording Web Services Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
|06/28/17||General||Under Shipping Control||X|
This release contains the following new features and enhancements:
- The Elasticsearch templates (call_recordingv2_template.json and screen_recordingv2_template.json) have been updated. Deploy the new versions of these templates to the Elasticsearch cluster so that when an index is created, the new index template is used. Re-indexing is not required after this step.
- Support for Red Hat Enterprise Linux version 7.
Interaction Recording Web Services now supports the following new APIs: Get Recording by ID, Get Recording Media by ID, and Delete Recording by ID. For more information, refer to Genesys Interaction Recording API.
Note: Support for the Delete Recording by ID API is added on July 14, 2017.
- Interaction Recording Web Services now supports using Java Runtime Environment (JRE) 8 as an alternative to the Java Development Kit (JDK) 1.8.
- The Cassandra schema used by RWS has been updated to version 188.8.131.52.
This release contains the following resolved issues:
The enableStaleSessionsMonitoring parameter has been removed from the sample application.yaml file. The default value for this parameter is false. Previously, this parameter was set to true for the Interaction Recording Web Services (RWS) nodes. If you have previously configured a value for this parameter, you must remove it from the application.yaml file on all RWS nodes. (GIR-12451)
You can now migrate to the Elasticsearch schema version 2, even if the crRegion setting found in serverSettings within the application.yaml file has special characters. For example, /MSN/USW1. Previously, it was not possible to migrate if the crRegion setting had special characters. (GIR-12266)
The MLM backup mechanism now validates and only accepts three "/" characters in the prefix of the file location, for example, to "file:///". Previously, a backup location that did not contain three "/" characters would result in an attempt to back up to an incorrect location. (GIR-12259)
The description of the value for path.conf in the sample elasticsearch.yml is now updated. Previously, path.conf contained a wrong value. (GIR-12133)
The createTime property returned by the Getting all labels from a recording API and by the Getting a specific label from a recording API is now returned in UTC. Previously, the value was in an incorrect timezone. (GIR-11944)
The response to a successful update when applying a label to multiple recordings now contains the path to the correct label instances. Previously, the path properties were all referring to the first label in the request. (GIR-11193)
When creating a recording with label data, if any mandatory attributes are missing, a 400 Bad Request response with status code 1 (RequiredParameterMissing) is now returned. Previously, status code 2 (InvalidRequestParameter) was incorrectly returned. (GIR-11805)
The Cassandra schema must be manually upgraded to version 184.108.40.206. Refer to Upgrading Interaction Recording Web Services.