New Features
Key | T | Resolved Date | Release Notes Subject | Release Notes Content |
---|---|---|---|---|
JTELDEV-6628 | Call Logging with ASR | 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. | ||
JTELDEV-6074 | Migration of Innovaphone Connector Service to .net 8 Core | The Innovaphone Connector Service is upgraded to .net 8 Core | ||
JTELDEV-6583 | Improvements to Logging for REST and TaskScheduler Processes. | The name of the task scheduler job is now shown in the call log under the column “Calling Party Number”. | ||
JTELDEV-6582 | Logging - Adding capability to remove non-call logs in portal. | It is now possible to delete non-call logs from the portal that are older than a maximum age parameter. The paramater name is “Portal.Statistics.CallHistoryPartA.NonCallLogs.MaxAgeDays”. | ||
JTELDEV-6523 | 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
Key | T | Resolved Date | Release Notes Subject | Release Notes Content |
---|---|---|---|---|
JTELDEV-6591 | CONNRES in DB may be incorrect on outdials | On outdials when the call was refused by the connected party, the CONNRES values could be incorrect. This problem has been fixed. | ||
JTELDEV-6647 | ACD-G-014 - group rules "Request Callback 2" and "Request Callback 3" not counted in report | In ACD-G-014 the group rules "Request Callback 2" and "Request Callback 3" were not counted in report. This problem has been fixed. | ||
JTELDEV-6633 | 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. | ||
JTELDEV-6627 | InputMenuDTMFASR object - Error Annoncement and Error TTS text is not used. | The IVR object InputMenuDTMFASR is not using the error announcement or the error TTS text. This problem has been fixed. | ||
JTELDEV-6624 | 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. | ||
JTELDEV-6619 | ACD-S-007 - parameters ordered incorrectly | The parameters “service level seconds” and “hangup seconds” were used the wrong way round when calculating the report. This problem has been fixed. | ||
JTELDEV-6356 | Agent Home Display - Files not updated in browser after portal update | A cache control filter has been implemented in the portal, to control how the following files are updated by the browser:
This should alleviate the problem that incorrect CSS and JS and images could still be displayed after a portal update. | ||
JTELDEV-6600 | 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. | ||
JTELDEV-6608 | Reports - ACD Agent Report 3 - ACD-A-007 - Wrong Acd Post Calls Duration and Average. | The calculation of Acd Post Calls Duration and Average in the Report “ACD Agent Report 3 - ACD-A-007” was wrong. This has been fixed. | ||
JTELDEV-6612 | Support of (very) old report subscriptions in new portal versions | Very old report subscriptions were created without the ClientsID parameter, which would cause them to fail with an error. This problem has been fixed. | ||
JTELDEV-6597 | 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. | ||
JTELDEV-6442 | Manual Callback - Message Template not updated when group is changed | When creating a manual callback event, the message template was not updated when the ACD group was changed. This problem has been fixed. | ||
JTELDEV-6599 | IVR Object - REST Query does not work. | 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. | ||
JTELDEV-6580 | Subscription E-Mails without an Attachment | Sometimes subscription emails could be sent without an attachment. This problem has been fixed. | ||
JTELDEV-6566 | Redistribute after Agent Logout/Login | The chat should be distributed to the previous agent if it is only one free option. | ||
JTELDEV-6574 | Acd Groups - Synonyms import - Tarif can be empty and phone numbers should be checked. | The Synonyms import in Acd Groups was not working properly, the following two problems existed:
This is now fixed. | ||
JTELDEV-6576 | Transaction Codes - list is misbehaving. | 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. | ||
JTELDEV-6581 | No Selected ACD Group on Outdial from Callback | Sometimes, an outdial from within a callback event would fail with “No Selected ACD Group”. This problem has been fixed. | ||
JTELDEV-6579 | 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:
|