New Features
Key | T | Resolved Date | Release Notes Subject | Release Notes Content | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
JTELDEV-6744 | Dialler - Addition of "Skip" and "Dial Now" Buttons in Dialler Contact Preview | We have enhanced the dialler's contact preview functionality by introducing two new buttons:
| |||||||||||||||||||||||||||||
JTELDEV-6785 | PBX Users - New Fields and new Filter | The following fields have been added to the PBX Users Table:
The visibility of the fields is controlled using the resources:
The field Extra Data can use new lines in the data, for formatting the field’s content over several lines. The data filter in Agent Home, Agent Home Braille and the Mini Client can be setup to use a full text filter over the following fields:
This is set using the resource:
Note, by standard, this resource is set to “prohibit inheritance” and so it will not be active, even after an update. If you wish this functionality to be available on your system then you will need to setup this resource. If it is not set, the behaviour is as previously. If set, the filter behaves slightly differently to previously:
IMPORTANT NOTE:
| |||||||||||||||||||||||||||||
JTELDEV-6741 | GPT Bot - Now configurable via Web UI | It is now possible to create LLM based bots using the Web UI for the chat connector. A new tab “LLM” has been added. This contains the following settings:
The chat connector will then communicate with the LLM connector to execute the required functionality. Exactly what kind of conversation is had - depends totally on how you instruct the LLM in your prompt. | |||||||||||||||||||||||||||||
JTELDEV-6769 | Innovaphone Connector - Linux Support | The innovaphone connector can now be deployed on Linux using .NET Core. | |||||||||||||||||||||||||||||
JTELDEV-6764 | Dialler REST API - Contacts History not guaranteed to be sorted | When retrieving the contact history for a contact using the REST API, the contact history was not explicitly sorted. Whilst the database engine appears to retrieve the records in physical order (i.e. the order in which they were created) this behaviour is not documented and therefore not guaranteed. An ORDER BY clause has been added to ensure the contact history is in the same order as it was created. | |||||||||||||||||||||||||||||
JTELDEV-6742 | ACD-E-001 - Report Improvements and Additional Columns | The report ACD-E-001 has been extended. The following additional columns are provided:
Below each event, the sums of these columns are calculated. At the bottom of the report the summary includes the total, minimum, average and maximum values of the new columns (except for transaction codes) and the total number of events in the report. | |||||||||||||||||||||||||||||
JTELDEV-6736 | Workflow / IVR Applications - indexed variable access | It is now possible to access variables using indexes in workflow / IVR applications. This is achieved using an index variable. NOTE: THIS FEATURE IS ONLY AVAILABLE WHEN USING THE NEW TELEPHONY SERVER. Consider the following data, which could be returned from a REST API call: { "records": [ { "name" : "record1" }, { "name" : "record2" } { "name" : "record3" } ] } When the workflow engine parses the above data, the following variables will be created: $records.0.name = record1 $records.1.name = record2 $records.2.name = record3 $records.count = 3 Note the new count variable, which is added whenever a JSON Array is parsed. Now it is possible to use an index variable to access the individual records. Declare a variable $index and set it to 0. Consider the following expression: $records.$index.name Previously, the result of parsing this expression would have been: $records.0.name Now, if the variable parser replaces a part of an expression, it will attempt to parse the result again. This will result in the above result being parsed again, which produces the output: record1 | |||||||||||||||||||||||||||||
JTELDEV-6722 | IVR - new variable cockpit_result | A new variable cockpit_result has been added, which contains the result of the last cockpit variable function. This is set to 0 at the start of the call. After every cockpit variable operation, it is set to 1 if the operation was successful, and 0 if not. This can, for example, be used to limit the number of parallel calls within an application. The cockpit variable should be a counter, and the logic to increase the counter can be implemented with compare and increment. The increment is only performed, if the value is below a defined maximum value. The counter should then be decremented at the end of the call, if the value of the cockpit_result variable is 1 → which means the counter was successfully incremented during the call. | |||||||||||||||||||||||||||||
JTELDEV-6719 | Callbacks - Prepend the new message to the existing one when a duplicated callback is created. | When a duplicated Callback is created, it was just creating a new comment saying A further callback request was made by the caller. Now, it also prepends the new Message to the existing one. | |||||||||||||||||||||||||||||
JTELDEV-6717 | Report ACD-S-007 - Hangup Seconds and Service Level Seconds now selectable from 0 to 120 | In the Service Numbers Report ACD-S-007, the service level seconds are now selectable from 0 to 120 instead of the stepped ranges which were previously used. | |||||||||||||||||||||||||||||
JTELDEV-6710 | Acd Agent Performance Report - ACD-A-003 - new columns | The following columns have been added to the report:
A new option has been added which influences the calculation of “Ready Time” - Ready time includes ring time. If set, the calculation is as follows:
If not set, the calculation is as follows:
| |||||||||||||||||||||||||||||
JTELDEV-6593 | E-Mail Body Templates - Longtext templates now support html | If the template for the email body starts with <!DOCTYPE html> the body format is considered to be html, and the email format is set accordingly. |
Bugfixes
Key | T | Resolved Date | Release Notes Subject | Release Notes Content |
---|---|---|---|---|
JTELDEV-6566 | Chat Redistribution after Agent Logout/Login | The following use cases have been fixed:
| ||
JTELDEV-6778 | Mini-Client - Clicking on the Group tab results in a null pointer exception. | When using the miniclient and clicking on the Group tab, a null pointer exception was sometimes produced. This problem has been fixed. | ||
JTELDEV-6766 | 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: #{(not empty acdUserStatusBean.CRMLink) ? 'link:'.concat(acdUserStatusBean.CRMLink).concat('[').concat(acdmessages['AcdAgent.CRMLink']).concat(',window=_blank]') : ''} | ||
JTELDEV-6761 | Wildfly - Old caches are not deleted after Wildfly restart | When the web server is restarted, old caches were not deleted. This could lead to statistical errors in the Supervisor if the cache had become inconsistent because it should have been updated whilst the web server was stopped. This problem has been fixed. | ||
JTELDEV-6757 | Automatic Callback - Event is redistributed | When an existing callback event is automatically commented by the system, because the caller requests a callback once more, the event was erroneously redistributed by the system. Now, the callback event will remain in the same state when the comment is made. | ||
JTELDEV-6759 | EMail Connector - not possible to create a new incomming mail box | If no mailboxes were previously configured, then it was not possible to create the first new mailbox. This problem has been fixed. | ||
JTELDEV-6758 | Portal Front End - Spanish no longer selectable | Changing to spanish was no longer possible via the portal front end. This problem has been fixed. | ||
JTELDEV-6666 | 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. | ||
JTELDEV-6733 | 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. | ||
JTELDEV-6730 | Request Callback 3 - incorrect repeat count | The request callback 3 group action did not count the number of repeats correctly if no number was entered. This problem has been fixed. | ||
JTELDEV-6687 | Supervisor Wallboard - Service Level Gauge | The calculation for the service level gauge did not respect both servicelevel calculation methods. This problem has been fixed. | ||
JTELDEV-6727 | REST API - Dialler Functions | The ForeignSystemID is now set to UserData when a dialler campaign is cloned. This helps identifying the campaign later. | ||
JTELDEV-6714 | Reports - ACD-G-004 - Wrong percentage values. | The ACD-G-004 Report was showing wrong percentage values for the Total, Average, Maximum and Minimum in the following columns:
This has been fixed. | ||
JTELDEV-6715 | 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 fixed. |