The report ACD-S-002 - Service Numbers Report 2 - excel variant used the wrong template. This problem can be mitigated by deleting the file//acd-store/shared/Data/system/jasper/Statistics_ServiceNumbersReport2.xls.jrxmland is automatically fixed when an update to this version is performed.
CORS problem in Miniclient EXE using external login service
A CORS problem could occur when using the Miniclient EXE in combination with an external identity provider (reproducable with Octa). The mini client no longer sends stored cookies to external URLs, such as those of the identity provider’s login service, which prevents this issue.
An unnecessary reference to an unused library caused log4j version 1.4 jar to be present in the portal war file. This dependency has been removed. Please note, it is not necessary to patch existing installations, as the file was never used by the webserver.
InputASR Object - Add a new timeout: Timeout Between Words.
In the IVR objectInputASR, a new timeout has been added - “Timeout Betweeen Words“. This timeout defines the maximum value of silence between words. The default value is 1500 ms. Once this timeout has occurred, the ASR will calculate the final result.
MiniClient EXE - User-Agent http request header is configurable in config file
A new parameter was introduced to the the MiniClient configuration file:
BrowserUserAgentHeader
If the value is not empty, this overrides the user agent header used by the mini client EXE browser when it makes requests. If not configured, the value used is as follows:
Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 JTELMiniclient/2.0
It was not possible to remove the azure login button from the login screen, even if there was no azure authority configured in the client account. This problem has been fixed.
TTS Engines - irritating sort order of engines in the IVR GUI
The TTS Engine list in the IVR GUI dropdown lists was not sorted correctly. This resulted in de-AT and de-CH being at the bottom of the list, instead of above de-DE for example. This problem has been fixed.
FTP Upload - Upload call recordings into a second FTP server if configured in a second Client.
It is now possible to configure a second FTP server so call recordings can be uploaded to a second FTP server.
This is performed by creating a second client, then adding a Client parameterFTP.CallRecordings.CopyJob.ClientsIDin the first client which contains the Clients.ID of the new client.
The credentials for the new FTP server are created in the second client account, and the FTP jobs will be copied from the first client to the second client, resulting in two uploads.
A further parameterFTP.CallRecordings.CopyJob.UsersIDscan be used to constrain the users for which the job is copied. This parameter is provided as a comma separated list.
NOTE: do not put any spaces or other characters between the IDs - this will not work.
Supervisor - Cockpit Variables - very long name prevents operation of sliders
If a cockpit variable had a very long name, then the text would overflow out of the tile in the supervisor covering the previous slider (the one rendered above). This would prevent operation of the slider control. This problem has been fixed - the name is now truncated, the full name of the cockpit variable can be seen by moving the mouse over the shortened text.
Customizable Display Possibilities for Calls in Agent Home and Mini Client and usage of JSON Stuctured Data in Calls
It is now possible to customize three areas in agent home and the mini client, for the actual information displayed when a call is received.
The level of customization is high, the display of the information is based on asciidoc - a variant of a markdown language. With this highlighting and coloring is possible, tables can be displayed, and and number of individual links can be added. Even the display of graphics hosted on a separate server is possible.
Customization can either be applied globally, or on an individual ACD Group basis. Using the feature on an individual ACD group allows, for example, the greeting and group specific information or links to be displayed.
JSON data call be attached to the call in the IVR call flow, enabling much more data to be attached than previously. For example, a complete customer record with name, address and contact details, purchased products, etc. could be attached and displayed using an asciidoc template.