The Staface connector is packaged and deployed as a Docker container

ACD media event handling has been improved to make working with new events faster and more convenient.

When the new setting AcdEvents.OpenNextNotOpenedEvent is enabled, clicking the media event notification icon can open the next new event directly instead of only showing the event list and also open the related CRM record automatically when available. The next event is selected based on priority and waiting time, so higher-priority and older new events are handled first.

When the new setting AcdEvents.OpenCrmUrlOnOpenEvent is enabled, opening an event can also open the related CRM record automatically when a CRM link is available. This helps agents and supervisors access the relevant customer or case information more quickly.

A new action is also available in the transaction-code popup, allowing users to complete the transaction-code step and close the event directly in one flow.

1. MiniClient changes:
   A new helper application called SwyxCommander.exe was added.
   Its purpose is to interact with the SWYX phone software and automatically perform actions such as answering or controlling calls.

Two new MiniClient configuration parameters were introduced:

<value name="MCEventActive" type="Boolean">False</value>
<value name="MCEventHandler" type="String">SwyxCommander.exe</value>

Meaning:
MCEventActive - Enables or disables this functionality. False = disabled. True = enabled.
MCEventHandler - Defines which executable should process incoming events from the Portal. In SWYX case: SwyxCommander.exe

1. *Portal change*s:

The Portal now creates a hidden DOM element called: MCEventForDotNet
This element is not visible to the user. It is used only for communication between the Portal webpage and the MiniClient application.
The Portal fills this element with data in the following format: <timestamp>#<userId>#<command parameters>

Example: 1779108501907*#3216#*CLICKTOANSWER LU_GAP_01
Meaning:

1779108501907 - Current timestamp in milliseconds
3216 - User ID
CLICKTOANSWER LU_GAP_01 - Command parameters for the MiniClient/SWYX integration

A new Agent Label field has been added to the Chat Connector, allowing flexible configuration of the agent name displayed in the chat window. This provides more flexibility in how the agent name is displayed – for example, static text such as a department name can be entered, combined with dynamic variables.

The Agent Label field supports static text and/or the following variables:

• $agent Default - Agent's NickName (if set), otherwise Agent’s UID
• $agent_name Agent's name
• $agent_firstname Agent's first name
• $agent_uid Agent's UID

These variables are also available when composing messages under Configuration Template.

New outlook has limited or no native support for opening .eml files, unlike classic Outlook.

1. Introduced a new boolean user property AcdAgent.MediaEvent.Email.Download.AsMsg in Portal GUI. When enabled (true), emails are downloaded in .msg format instead of .eml, where available. This feature requires IMAP Connector version 3.1 or higher.
2. A new configuration parameter MsgAnswerDetectionAlgorithm has been introduced in IMAP Connector. It supports the following values: "Subject", "Body", and "Both".

Depending on the selected value, an additional identification token will be inserted into the generated .msg file:

• Subject: the token is added to the email subject
• Body: the token is embedded in the email body (hidden)
• Both: the token is added to both subject and body

Example:

• Subject: Re: Subject request 2344
• Body: <div style="display:none">ID=2344</div>