Page History

The parameter Portal.TaskScheduler.MaxAgeDays controls the new cleaner for the task scheduler. This cleans up tasks which are in the DONE state and are older than the configured number of days. Note, that tasks which are reqired as templates for cloning should simply be set to the READY state and deactivated. Do not leave a task in DONE if it is to be used for a clone.

The Dialler CTI mode had an erroneous button display when the result code popup was displayed. This problem has been fixed.

The object categories and the contained objects in the sidebar of the GUI (object selection) are now sorted alphabetically for the user’s selected language.

The task scheduler could hang on non-repeating tasks which were being rescheduled erroneously. This problem has been fixed.

In some IVR GUI objects, when a selection is made the size of the popup changes. This could result in the “Close” button being still visible, but slightly cut off at the bottom of the popup. This problem has been fixed.

The Cisco jtapi PBX connector now supports release 14.0.

The call log analyser now provides access to the detailed r5 logs for all legs of the call. Within the web based call log for the main leg of the call, links are provided which show the logs of the related processes.

The new Teams profiles feature allow the client administrator to create Teams profiles. Within the profile, he can create Teams rules and assign users. User assignment can be the other way round: from the Users master data.

Another function is added which is the ability to copy Teams profiles from a source profile. Also, the ability to copy Teams rules from a source user.

For more information, see the link: https://wiki.jtel.de/x/OIdhB

Voicemails and callbacks that was not generating a media event because nothing was recorded or the recording was too short were counted in the report. This has now been fixed.

Before, in supervisor view → All/Active Agents → Quick Status Buttons, the supervisor was able to change his or other agents statuses to statuses that are restricted in the logged in group. this bug has been fixed.

The Teams presence connector was returning an error when the agent/user name is too long (More than 64 characters). This has been fixed now and the maximum length of the name is set to 256 characters.

The bean initialization/refresh algorithm is corrected.

The ACD-Transaction-Codes-Report 2 was missing the group (s) name (s) when executed with the XLS format. This has been fixed.

The task scheduler provides the capability to run tasks at scheduled times, optionally repeating them as required.

It has the following capabilities:

• Run a telephony task on a specified date and time by making an outbound call to a destination and starting the application configured on a service number

• Run a workflow task on a specified date and time by starting a background daemon process and running a workflow (GUI) application

• Reschedule the task on completion for a time in the future

• Retry the task if it fails to start or fails to complete

• Start an error task (as a background process) if the task exceeds the maximum number of tries before it completes

More documentation on the task scheduler can be found here: https://wiki.jtel.de/x/_oRhB

Before this fix, the chatbot services were not restarted automatically when rebooting the chatbot server. This has been fixed and all active chatbot services will restart automatically after the reboot.

The rest call for the event Ringing, configured in Acd Group Parameter is not working. This problem has been fixed.

Previously, if the group action “Call Back or Voice Mail” was used, the statistics would always count the resulting event as a callback, even if it was a voice mail. Now, once the user has made the choice by DTMF, the type of group action is changed in the statistics table to the actual type of event booked.

For the ACD Group Parameters which configure REST calls during the call flow, the following variables have been added:

$agent_email - the email address of the agent

$call_duration - the duration of the call in seconds

See https://wiki.jtel.de/x/ZIZhAg for more details.

The user is not able to call dialler contacts because he is stuck in TAC status. To reproduce this problem, you need to do an outbound call from a callback event and set a TAC, then start a dialler.

The user is not able to set a result code and the popup hangs. This problem has been fixed.

The presence connector throws exception when PBX Users are duplicated. This problem has been fixed.

Additional subscription path is converted to Linux path.

The IVR object Run Script ended the call when the script triggered errors. This has been fixed and the IVR object has now an error output. Please note, this will require replacement of the object in routing applications if you wish to take advantage of the error output.

A space in the agent name or surname would break the FTP upload. This problem has been fixed, spaces are now URL encoded with %20 before uploading.

ACD-Transaction-Codes-Report 3 - ACD-TAC-003 - there were missing spaces between the TAC counters in the TAC warning when the maximum number of TACs was exceeded, and also between the date output in the header. This problem has been fixed.

The incoming event blinking circle was moving when scrolling. This has been fixed.

The field “Overwrite CRM-Url with CRM-Url from IVR” is displayed in Standalone, Configuration AND Agent groups, while it should only be displayed in standalone and configuration groups. This has been fixed.

New variables are defined to include the agent's name, the agent's first name and the agent's number in the name of the outgoing call recording file.

These variables are: $agent_name, $agent_firstname and $agent_number.

The persistent busy and persistent no answer displays are no longer applied to outbound calls.

For outbound calls, the calls tab in Agent Home now displays the outbound text corresponding to the CONNRES for outbound calls, and not the group end reason. The agent end reason is left empty for outbound calls.

An encoding problem was found when using the REST API to execute a routing application. This problem has been fixed.