Release 3.22

When making outbound calls, the mini client popup window for making outbound telephone calls and recording transaction codes did not resize well when the mini client was reduced below a certain size. This problem has been fixed.

When an email has been responded to, the response email is also displayed in the agent client when the event is viewed again.

A deleted user can still be seen in locked accounts. This is by design: the locking of accounts is stored in a different table to the user accounts, and hence this can still be seen after the user is deleted. This can, for example, be useful when an account is first of all deactivated, to detect if the user still tries to login to the account.

The UserSearch Object now supports searching for users by the Nick Name field. This is particularly useful when an external system does not use the same user UIDs as the jtel system.

The chat connector server can now be installed using systemd instead of init.d

The outbound call popup would not appear in some scenarios, particularly if both of the following resources were not allowed:

portal.Acd.AgentHome.CallProcessing.Outbound.UserDefined
portal.Acd.AgentHome.CallProcessing.Outbound.UserCommunication

This problem has been fixed.

There was an error in the selection of service numbers by billing number in Service Numbers Report 5 and 6. This problem has been fixed.

A connector for Microsoft Teams is available. The connector imports the teams status of users from the office 365 cloud, and displays this information in various views in the system including the agent views and pbx user views in agent home and the supervisor. The user's own teams status is displayed in the header in the portal.

Further features are planned which will enable call and event distribution to be dependent on the status of users in teams.

Users can configure the system to play a sound when new or updated chat messages are received. This feature is enabled by users their own account settings.

The REST interface now supports the creation of callback and ticket events. See https://wiki.jtel.de/display/JPW/REST for further details.

A new set of APIs has been added to the REST interface to retrieve ACD groups. 3 functions are provided:

BaseURL/ClientsID/acd/groups - retrieves a list of all ACD groups in the client account.
BaseURL/ClientsID/acd/groups/group/ID - retrieves a specific ACD group by ID
BaseURL/ClientsID/acd/groups/group?name=Name - retrieves a list of ACD groups using the Name as a match.

Note, the last function may return more than one record, as a partial match is used.

A new set of APIs has been added to the REST interface to retrieve users. 3 functions are provided:

BaseURL/ClientsID/users - retrieves a list of all users in the client account.
BaseURL/ClientsID/users/user/ID - retrieves a specific user
BaseURL/ClientsID/users/user?uid=UID - retrieves a list of users using the UID as a match.

Note, the last function may return more than one record, as a partial match is used on the UID.

A query parameter has been added to the function GET BaseURL/ClientsID/dialler/contacts allowing the specification of the dialler campaign ID from which to retrieve the contacts list.

The autoincrement ID could overflow in the JTELStats2.Compressed* tables, meaning that no more values could be inserted in the tables, in particular CompressedU15 was affected by this. The autoincrement ID field has been changed to a BIGINT to fix this problem.