You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

New Features

KeyTResolved Date Release Notes SubjectRelease Notes Content
JTELDEV-6699StoryBraille Agent Home Improvements

The following functions have been added to Braille Agent Home:

  • Using the “Dial” (Outbound) functionality whilst in a call is now 100% equivalent to using the call transfer to number functionality
  • The ACD Agent Status Popups and mini buttons are no longer shown - the long “textual” buttons are shown anyway so these functions were redundant
  • The impersonation area is shown, if another user has changed to the Braille user’s account.
  • The logout link is now available.

Documentation of how to setup Braille Agent Home is now available here: https://wiki.jtel.de/display/JPW/Braille+Agent+Home

JTELDEV-6623MiniClient - Code Signed

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.

JTELDEV-6618Accessability Improvements

Some accessability improvements have been made to the portal including:

  • Removal of tab stops on the burger menu
  • Automatically focussing the first input field on some commonly used popups
  • Removal of unnecessary clutter for better use by screen readers on agent home braille
JTELDEV-6649Video Server - Add new option: ChatEnabled.

This new feature allows users to generate the embedded code to enable the chat function on the video server. If the ChatEnabled option is set to true, then the caller should have a chat button and a chat window should open automatically.

JTELDEV-6638Notifications - Incoming Chat and Incoming Media Events

It is now possible to customize the notification sounds played when an incoming chat or incoming media event is received by an agent.

The configuration can me made as a client administrator under “Client Master Data” … “Options.

If not configured, the standard sound files are used as previously.

JTELDEV-6656StoryNetwork IVR Lists - Add Longtext column "Extra Data".

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.

Bugfixes

KeyTResolved DateRelease Notes SubjectRelease Notes Content
JTELDEV-6695BugPrompts - Master Data - Dependencies

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.

JTELDEV-6700BugOutbound Calls - Call Transfer to Group (blind)

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.

JTELDEV-6694BugEditing 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.

JTELDEV-6689BugChanging 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.

JTELDEV-6680BugACD-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.

JTELDEV-6683BugManual postcall handling fixes

Manual post call time was not always added to the post call time for the last call. This problem has been fixed.

JTELDEV-6679BugReports - Missing transferred calls in reports ACD-A-001, ACD-A-001-02, ACD-A-002, ACD-A-002-02

In the following reports, transferred calls that are not connected are not counted:

  • ACD-A-001 ACD Agent Calls Report 1 - itemised agent calls by date / time
  • ACD-A-001-02 ACD Agent Calls Report 1 - 02 - itemised agent calls by date / time
  • ACD-A-002 ACD Agent Calls Report 2 - itemised agent calls by service number
  • ACD-A-002-02 ACD Agent Calls Report 2 - 02 - itemised agent calls by service number inbound and outbound

This problem has been fixed.

JTELDEV-6675BugNew 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.

JTELDEV-6662BugLanguages - Change portal language code es-SP to es-ES.

The Portal Language code es-SP is now changed to es-ES.

JTELDEV-6646BugMini Client - Input texts get out of/exit the Callback and Call popups when the width is really small.

When setting the Mini Client width really small, the input texts fields get out of/exit the Callback and Call popups. This is now fixed.

JTELDEV-6604BugSAP Connector - Accept call from SAP doesn't work.

Using the SAP connector to accept an incoming call does not work. This probelm has been fixed.

JTELDEV-6566BugChat Redistribution after Agent Logout/Login

The following use cases have been fixed:

  • Only two agents are logged in. Agent 1 received the chat and logged off, the chat was distributed to the 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.
  • No labels