The jtel MiniClient .EXE is now code signed. Note, this will not automatically stop the “smart screen” warnings. According to Microsoft we will just have to wait and see - it could take anywhere betweeen 2 and 4000 downloads and checks by smart screen before it stops displaying warnings, and in fact there is no guarantee that this will ever happen. The code signed .EXE should display JTel GmbH, Alte Landstr. 29, 85521 Ottobrunn, Bayern, DE as the signing entity, issued by GlobalSign GCC R45 EV CodeSigning CA 2020.
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
Bugfixes
Mini-Client - Clicking on the Group tab results in a null pointer exception.
When using the miniclient and clicking on theGrouptab, a null pointer exception was sometimes produced. This problem has been fixed.
Agent Home - CRM link is not clickable when not using http or https
In Agent Home and the Mini Client, the CRM link was not clickable if it used a non standard scheme other than http or https. This problem has been fixed.
From release 3.39, the following method *#
{acdUserStatusBean.CRMFormattedLink}
* is available to the Asciidoc functions library to display the CRM Link correctly when customising the layout.
Prior to release 3.39 a workaround is specifying the link as follows in the layout:
TAC - Incorrect TAC display when using the transfer type ‘Transfer with query options’
The problem can be reproduced by performing a complete group transfer to a group in which no agent is connected. As soon as the call is in the queue, we connect an agent and answer the call. If the original and the target group have different TACs and the transfer type is ‘Transfer with query options’, the transferred agent receives a TAC popup with incorrect content. This problem has now been fixed.
Dialler - Result Code Popup too small to show all the content in Mini Client.
The Dialler Result Code popup was too small to show all the content when used in Mini Client. A scrollbar has been added to the popup which allows the display of the full content, in particular when an appointment is being set.
Manual Dialler - Editing a dialler contact leads to an incorrect tab
In the manual dialler, when a dialler contact is edited and saved or the save is cancelled, the wrong tab is displayed subsequently. This problem has been fi
The dependencies (usage of a prompt) displayed the name of the version of the IVR application in which it was used. This has been improved to display the name of the routing application and the name of the version.
Transferring an outbound call to another group would cause errors in the call flow and hanging lines on the telephony server. This problem has been fixed.
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.
New Telephony Server now supports supervisor mute / unmute functions
The new telephony server now support the supervisor mute and unmute functions, which enables muting / unmuting of the supervisor to work properly.
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.
Sometimes, an outdial from within a callback event would fail with “No Selected ACD Group”. This problem has been fixed.
free Agent 2. If this agent also logged off, but meanwhle Agent 1 had logged back in, the chat was no longer distributed to Agent 1 again.
Two agents are logged in. The chat was being offered to Agent 1 or was currently being worked on by Agent 1. Agent 1 logged out. The chat was not redistributed to Agent 2 immediately.
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)