This new feature allows users to generate the embedded code to enable the chat function on the video server. If theChatEnabledoption is set totrue, then the caller should have achat buttonand achat windowshould open automatically.
A new column called "Extra Data" in Network IVR Lists has been introduced.
This column can be used to store a larger data fields - typically in JSON format.
The List Functions and List Functions Variables IVR objects have been updated to support the new column for the function: “Add Value to List”.
The List Lookup and List Lookup Variable IVR objects have been updated to be able to store the new column value in a variable.
Note: The list lookup function only uses Field 1 to Field 4 for matching as the new column Extra Data is not indexed and not designed to be used within a search.
The web call logs now include the unrecognised utterances from callers when the ASR is used. The unrecognised utterances are grouped into one log, which is output just before the object being used is exited, or a hangup is processed.
IMAP Mail Connector - now supports OAUTH2 authentication
OAUTH2 authentication for the IMAP mail connector has been implemented.
Note - since Microsoft 365 no longer supports OWA / Exchange Mail Services, replacement of the exchange mail connector will be necessary on systems which use older style access to Microsoft email services in the cloud. If you require assistance with this, please contact your jtel partner or check out this link:https://wiki.jtel.de/x/PQA0Bw
Editing Routing Applications - Edit Button is sometimes disabled
The first person to login to the web portal after a web server restart would determine the “editability” of routing applications for all users on that webserver. If the user logged in with the mini-client or a teams client, then no users on that webserver would be able to edit routing applications. This problem has been fixed.
Changing to Manual Post Call in Transaction Code Window - Sometimes a call was received
Sometimes when changing to manual post call when closing the transaction code window a call could still be received if the system had queued calls in this instant. This problem has been fixed.
ACD-TAC-001 - shows doubled up entries if a call is transferred
If a call was transferred between two agents, and both recorded a TAC, then ACD_TAC-001 would show both TACs twice in the report. This problem has been fixed.
Acd Supervisor - Agents Table has wrong Totals when not all Groups are visible.
When you select just a part of the Groups to be visible in Acd Supervisor, the Totals in the table “Agent” shows wrong values including the Groups which are not visible for some of the columns. This problem has been fixed.
Click to Dial with blazar telephony server - unneccessary error in blazar error log file
When an agent performs a click to dial using the new blazar telephony server, an exception is produced in the blazar error.blog file if the option “Run Routing Application after Agent Call (Outbound)” is set on the service number. This does not cause an operational problem on the server or within the call flow.
Media-Event - Incorrect TAB change when blinking envelope is clicked on in Mini Client.
When clicking the blinking envelope in Mini Client while having an active call, the Tab was changing to a wrong Tab while it should be changed to Media Event Tab “ME“. This has been fixed.
Media Event should not be distributed to Agent when he has an outstanding mandatory transaction code to be set.
An Agent who has an open mandatory transaction code popup was still able to receive media events. This has been fixed and the event is now distributed only after he sets the transaction code and closes the popup.
Using the IVR object REST query leads to the following error: curl not exist. This problem has been fixed and the curl command could be executed by 8server or blazar.
The list tab in Transaction codes was misbehaving: it shows duplicated Transaction codes for every group mapping. This is now fixed and the list shows no duplicates.
Salesforce - Click to Dial not working if system cannot determine if the salesforce instance is a sandbox or production instance
Click to Dial fails with a configuration error popup if the check whether the instance is a sandbox or production URL fails. Now this logic has been changed to use the following strategy:
if the URL starts with cs. it is a sandbox (customer sandbox)
if the URL container .sandbox. it is a sandbox
If the url starts with dev- it is a sandbox (developer)
If the url contains dev-ed. it is a sandbox (developer edition)