COMING SOON
New Features
Key | T | Resolved Date | Release Notes Subject | Release Notes Content |
---|---|---|---|---|
JTELDEV-6482 | Workflow Engine - New Variables $date_iso and $time_iso | Two new variables have been added to the workflow engine:
| ||
JTELDEV-6483 | TTS in IVR - SSML can now be used within texts without providing a complete SSML document | SSML can now be used within texts of the TTS and related objects without providing a complete SSML document. For example, previously the following was required: Previously the input would have to have been complete SSML, for example: <speak xmlns="http://www.w3.org/2001/10/synthesis" xmlns:mstts="http://www.w3.org/2001/mstts" xmlns:emo="http://www.w3.org/2009/10/emotionml" version="1.0"> <voice name="en-GB-LibbyNeural"> Your next appointment is on <say-as interpret-as="date" format="dm">21/03</say-as> at 09:00 </voice> </speak> Now, the system creates this automatically using a template, so the only part which needs specifiying is the content: Your next appointment is on <say-as interpret-as="date" format="dm">21/03</say-as> at 09:00. | ||
JTELDEV-6467 | ACD-S-007 - Service Numbers Report 7 | A new Service Numbers Report 7 has been added. See https://wiki.jtel.de/x/AYAfBw for details. | ||
JTELDEV-6460 | User master data - capability to prevent user changing their password | A user can edit their password in User Master Data if the following resource is activated: "portal.UserData.User.ChangePassword" (activated by default). If deactivated, the user can no longer change their password. The same applies to editing the PIN using the resource "portal.UserData.User.ChangePIN". | ||
JTELDEV-6466 | New Report ACD-A-016 - Agent Status Report Sums | A new report New Report ACD-A-016 - Agent Status Report Sums has been added. This sums ACD agent status over the selected time period. See https://wiki.jtel.de/x/eYDoBg for details. | ||
JTELDEV-6456 | Workflow Object Variable Declaration - Now accepts an empty value | The workflow object Variable Declaration now accepts an empty value without producing a warning. | ||
JTELDEV-6454 | Workflow Object User Search - Search by Email Address | The workflow object User Search now has a parameter to search by the user’s email address. Also, the following new variables have been provided on a successful search:
And when the search fails because more than one user was found, the following variable is provided:
| ||
JTELDEV-6437 | Single Sign On with OAUTH2 (for example Okta) - Misleading "azurelogin" redirect URI | The misleading "azurelogin" redirect URI has been replaced with “ssologin“. Note: the functionality is the same, this change was made with respect to questions received from customers when configuring. | ||
JTELDEV-6443 | Extra Variables in for Service Number Parameters added to Routing Application | The following additional variables have been added to the a service number parameters:
The new text parameters are edit fields which can be used for anything. | ||
JTELDEV-6415 | Live Agent AI Integration | In agent home in the full web client it is now possible to integrate AI modules to aid in the processing of the conversation. The following features are available:
NOTE: This feature requires special activation by jtel and may require additional licenses. Please contact jtel for details. | ||
JTELDEV-6397 | ACD Events - capability to hide send to agent and send to group | The following resources can be used to display or hide the capability for agents and supervisors to send ACD events to other agents and other ACD groups.
Note: the following exising resource is used to hide the capability to send an event by email:
| ||
JTELDEV-6391 | Agent Home and Mini Client - New option to play sound when media event is received | A new option has been added to play a sound when a media event is received. This can be toggled in the mini client footer, or in the user master data settings. | ||
JTELDEV-6361 | Agent Home Improvement on callback handling. | When a call is made from a callback event associated with an Agent Group, the ACD group used to make the call (i.e. set the outbound telephone number) now can be selected from the call dialog – a configuration or standalone group can be selected. | ||
JTELDEV-6379 | IVR: Object Create AcdEvent Advanced now available with variable parameters | A variant of the IVR Object Create AcdEvent Advanced is now available with variable parameters. | ||
JTELDEV-6366 | AcdEvents - Extended Functions for Appointment and Priority | It is now possible to create ACD events with a priority and an optional date for an appointment. The following changes have been made: Priority Events in the queue are now sorted according to priority, highest first, then according to the received date, oldest first. If no priority is specified (or for old existing events) then a value of 50 is used. Appointment Date & Time An appointment date / time can be specified. Events are not distributed before this date and time if specified. When an event is created, the following rules apply regarding the date and time:
Note: the actual distribution depends on the agents logged in and the distribution requirements (skill, priority etc.). Features Updated to Support New Functionality
| ||
JTELDEV-6340 | Call Recording - Override call recording mode after opt-out by caller possible | In some scenarios, it is desirable for agents to be able to activate call recording manually even if a caller has opted out of the recording previously in the IVR or ACD by pressing a DTMF in the appropriate menu. A new option has been added to the ACD group configuration for call recording:
This enables manual call recording, after the caller opts out of the variant of call recording configured in the ACD group. The agent can now see whether an opt-in or opt-out has been performed by the caller clearly in agent home and in the mini client. The following WIKI page details the call recording options and processing: And the new option configurable in the ACD group is documented here: | ||
JTELDEV-6253 | Outbound Calls - Run IVR Application after Agent Call | It is now possible to run IVR applications after a dialler call or click to dial outbound call. To use this feature, the following must be done:
Note, if the service number is configured to directly enter the ACD, then this would be a nonsensical configuration. The service number should be configured to run an IVR application when this option is set. Then the following modifications should be made to the IVR application:
| ||
JTELDEV-6362 | IVR Debug Variables - now creates a variable dump in the log for all server variables | The IVR object Debug Variables now creates a variable dump in the .r5log (old telephony server) or .blog (new telephony server). | ||
JTELDEV-6342 | Manual Callback - Add custom variables to manual callback body text | It is now possible to add custom data to the body of a manual callback, which may come from an external system or user inputs in the IVR. This is performed in two steps:
For example: saving the following JSON Data to the call: * { “customerNumber“: “123456”, “customerName”: “John Doe“}* will provide the variables $jsonData.customerNumber and $jsonData.customerName which can be used in the Long Text for the callback event. |
Bugfixes
Key | T | Resolved Date | Release Notes Subject | Release Notes Content |
---|---|---|---|---|
JTELDEV-6457 | Workflow Objects AcdEventsCreate Advanced and AcdEventsCreate Advanced Variable - Sending to a user directly would not distribute the event correctly | When using the workflow objects AcdEventsCreate Advanced and AcdEventsCreate Advanced variable - Sending to a user directly would not distribute the event correctly. This problem has been fixed. | ||
JTELDEV-6371 | E-Mail Client - Answering via Outlook closes the ACD Event.e | When answering an email via Outlook, the ACD Event was automatically closed as well. This is now fixed and the ACD Event will still be open. | ||
JTELDEV-6441 | Agent Home - Encoding problem while creating manual callback during a call. | During a call, the manual callback popup was showing the callback message (or subject) with an encoding problem if it has special characters. This problem has been fixed. | ||
JTELDEV-6447 | AcdEvents Create Advanced - ' in event subject or data causes creation of event to fail | A ' character in either the event subject or the event data caused the creation of the event to fail. This problem has been fixed. | ||
JTELDEV-6063 | Outbound calls - Add error messages if there is misconfiguration. | When there is a misconfiguration in the host file of the 8-server machine or if “dialler.8Server.IPs” parameter is set incorrectly, an outbound call (Click to dial or dialler) could not be executed, but no error message was shown. this problem has been fixed and the following error messages are now shown:
| ||
JTELDEV-6153 | TAC - Agent is able to set TAC when the supervisor connect via Monitor/Silent call | When the supervisor monitors the call and connects to the agent, the TAC is gone and the agent cannot set a TAC. This issue has been fixed and only the agent could see the available TACs and set them. | ||
JTELDEV-6436 | Prompts - changing the prompt type of an existing prompt kills the announcement | Changing the prompt type will change the filename in the database but not in the disk share. This will result an erroneous announcement file. Changing the prompt type is now disabled for existing announcements. | ||
JTELDEV-6426 | NOT CRITICAL - log4j-1.2.14.jar was present in the deployment package for the web application | log4j-1.2.14.jar has been removed from deployment package for the web application. Note: it was never loaded by the webserver, so no potential security risk was present. | ||
JTELDEV-6411 | Holiday Lists - Filter does not work | The filter did not work in the Holiday Lists view. This problem is fixed. | ||
JTELDEV-6410 | Call Flow - music on hold not played when agent transitions to blind transfer to group after using call HOLD before initiating transfer | The following use-cases in the call flow have been fixed:
In some cases, this could cause the music on hold not to be played after the last step. This problem has been fixed. | ||
JTELDEV-6419 | Agent Home and Mini-Client - Call Updates | In some cases the reporting of “ringing” when receiving an incoming call in agent home cloud be delayed more than necessary before the agents could see the information that the calls were being delivered to them. This problem has been fixed. | ||
JTELDEV-6420 | STARFACE connector - PBX Users status not being updated correctly | In some cases the PBX users status was not updated correctly. This problem has been fixed. | ||
JTELDEV-6326 | Teams Plugin - Report download fails | The downloading of reports would fail in the “new teams” application. This problem has been fixed. | ||
JTELDEV-6407 | Wrong redirection when the main portal login URL is used for miniclient executable configuration. | The redirection condition is corrected when main portal login URL is configured for miniclient executable. The cash directory name is provided with suffix to prevent version collision in cache storage. The major version of CEF is used as a suffix. | ||
JTELDEV-6402 | SSO Login (Azure, Okta, etc) - white screen if an email is configured in several users. | The problem only occured if several User accounts in the client account had the same email address. The problem has been fixed. | ||
JTELDEV-6387 | Manual callbacks created with Configuration Groups are not distributed correctly. | Creating a manual callback using a Configuration Group should distribute it to the Primary configured Agent Group. This was not always the case. The problem has been fixed. | ||
JTELDEV-6383 | AcdEventsCreate Advanced - save skills 1, 2 and 3 | The IVR object ‘AcdEventsCreate Advanced’ and ‘AcdEventsCreate Advanced Variable’ are not saving skill 1, 2 and 3 into the database. This problem has been fixed. | ||
JTELDEV-6346 | Azure Login - No information about login configuration problems. | No information is showed in case of a login error when the configuration is not correct. This problem has been fixed by displaying the full exeption message in the login dialog. | ||
JTELDEV-6350 | Task Scheduler - error in server process (no effect on actual running of the tasks) | An error was produced in the server console when a task was scheduled and the error task was to be run. If not configured, this would result in an error in the telephony server console. Note: the rescheduling of the task would proceed as normal so there was no impact produced. This problem has been fixed. | ||
JTELDEV-6343 | jrest - Routing Application Runner selects incorrect server | When using the the routingrunner function: *rest/v1.0/ {clientsID}/routingrunner/run/ {routingApplicationsID}* the REST API could select the incorrect server to run the application in a multi-server environment. This problem has been fixed. | ||
JTELDEV-6332 | Chat - Send chat event to Agent or Group does not remove the event from the first agent. | When sending a chat event to another Agent or Group, the event remains open in the first agent and he can still send messages to the client, close, hangup and do all actions. This has been fixed, the event now disappears from the first agent and the view is redirected back to the previous page. | ||
JTELDEV-6331 | JSESSIONID in the URL should be ignored by the webserver | In some cases, the session ID could be added to the URL by the browser. The server incorrectly included this in redirects causing an ajax exception. This problem has been fixed. | ||
JTELDEV-6325 | Request Callback - Duplicate Callback Prevention Error | When an anonymous caller created a callback twice, the first created callback would erroneously be commented with “Caller requested another callback” when using request callback variant 1 and 3. This problem has been fixed. | ||
JTELDEV-6324 | Voice Mail Transcription - did not add transcription to voice mails sent by email | The Voice Mail Transcription did not add transcription to voice mails sent directly by email (distribute via ACD was set to false). This problem has been fixed. | ||
JTELDEV-6315 | Mini-Client - no sound was played on an incoming chat | The Mini-Client (both executable and web) did not play a sound when an incoming chat was received. This problem has been fixed. | ||
JTELDEV-6314 | Chat: both chat icon and event icon flashes when chat event comes in | The event and chat icons both flash when a chat event is coming up. This problem has been fixed. | ||
JTELDEV-6212 | Login: Language ID incorrect when logging in by cookie | The language ID was set incorrectly when logging in via a cookie. This problem has been fixed. |