Screen Recording Service
Note: Not all changes listed below may pertain to your deployment.
- March 29, 2017 (8.5.335.73)
- December 18, 2016 (8.5.330.64)
- September 27, 2016 (8.5.320.64)
- July 29, 2016 (8.5.311.13)
- April 1, 2016 (8.5.302.10)
- February 1, 2016 (8.5.230.23)
- Known Issues
March 29, 2017 (8.5.335.73)
What's New
Resolved Issues
December 18, 2016 (8.5.330.64)
What's New
Resolved Issues
- The Screen Recording Service (SR Service) is now able to process a screen recording correctly if the agent's details contain special characters. Previously, the SR Service was not able to process a screen recording if the agent's username contained a single-quote character. (GIR-8186)
September 27, 2016 (8.5.320.64)
What's New
Hot Seating
- Support for Hot Seating with the Screen Recording Service and Agent Desktop.
July 29, 2016 (8.5.311.13)
What's New
- The slowMachine parameter is now deprecated, and is replaced by the new vlcCloseTimeout parameter.
- The SR Service will now retry to upload all failed recordings after the next restart.
April 1, 2016 (8.5.302.10)
What's New
- During upgrade the SR Service moves old log files (from 8.5.220.xx and earlier) to the Logs folder and renames them using the old_ prefix.
- The SR Service Authentication Server now runs as a separate process.
- The SR Service now supports Monitoring and Alarming.
- The SR Service now supports error reports for Web Services and Applications.
- The SR Service log now uses UTC time instead of local time.
- The SR Service now uses UTC time as the timestamp for screen recording files instead of the local time.
February 1, 2016 (8.5.230.23)
What's New
- Support for SR Service on Windows 10 (32-bit + 64-bit).
- Support for SR Service Windows 8 / 8.1 32-bit.
- SR Service Auto-upgrade will only install digitally signed versions. Version Checksum verification is
deprecated (softwareChecksum parameter).
- Auto-Downgrade is disabled and the forceUpdate parameter has been deprecated.
- The allowedHosts configuration parameter was added.
- SR Service now adds a unique ID as part of the voice recording file name.
- SR Service Authentication server now runs as a separate process.
- If the Agent credentials are invalid (403) or missing when trying to upload a screen recording to Cloud, the SR Service will use another agent's credentials to upload the recordings and will log an appropriate log warning.
- SR Service log files have been moved under the Logs folder.
- The SR Service log now includes milliseconds.
- SR Service HTTPS certificate verification default behavior changed from False to True ("certificate" parameter default value).
- SR Service now supports:
- CSRF protection on local host communication with Agent Desktop.
- Session cookies for the local host connection with Agent Desktop.
- Separate configuration for the user Temp folder, Post Processing folder, and the Shared Recording folder using the following configuration parameters: userSavePath, postProcessingSavePath, sharedSavePath.
- SR Service Auto Updater will now only start after an agent logs in.
- The SR Service version can now be queried using the browser.
- The diskFreeSpaceLimit configuration parameter is now a client side parameter. Previously, it was a server side parameter.
Known Issues
There are currently no known issues.
Comments or questions about this documentation? Contact us for support!
