The date format supports an optional day shift [<simpledateformat>|<day shift>].
Example: ACDGroupsReport3[yyyy-MM-dd_HHmmss|-1].pdf generates a file using yesterday’s date.

Introduced a new feature that allows users to export and import the routing applications.

Salesforce announced that starting with Spring ’26, the creation of new Connected Apps will be restricted. Integrations must use External Client Apps (ECA) instead.

The Salesforce integration in the jtel portal has been updated to support authentication via the OAuth Client Credentials Flow, which is required when using External Client Apps.

A new configuration option “Use Client Credentials Flow” has been added to the Salesforce client settings in the jtel portal. When enabled, authentication is performed using the Client ID and Client Secret, and the fields Username, Password, and Security Token are no longer required.

Existing integrations using Connected Apps and username/password authentication continue to be supported.

The Salesforce documentation has been updated accordingly.

The daily database cleaner has been extended to support customer-specific cleanup procedures.

A new parameter Portal.Cleaner.CustomProcedures has been introduced. It allows defining a comma-separated list of customer-specific cleanup procedures that will be executed automatically as part of the daily cleaning process.

• Integrates Aristech TTS as a speech provider into FreeSWITCH.
• Works via the standard FreeSWITCH TTS interface using the speak application.
• Allows passing authentication parameters:
  • ARISTECH_HOST
  • ARISTECH_TOKEN
  • ARISTECH_SECRET
• Optional parameters:
  • UUID – enables per-channel event notifications
  • SAVE_FILE=1 – saves generated audio to /tmp/
• Generates structured JSON events (mod_aristech_tts::json) on:
  • Successful synthesis (includes audio size, duration, filename)
  • Errors (includes error code and detailed message)

The Starface 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>

A new Export button has been added to the Dialler Contacts view.
Users can now export all dialler contacts (across all campaigns) in CSV format directly from the Dialler Contacts screen.

When batch deleting dialler contacts via the REST endpoint /dialler/contacts using UserDataList, not all contacts sharing the same user data were removed and the REST interface could return misleading output. The batch deletion logic has been improved so that all dialler contacts with identical user data are now removed consistently.

Resolved an issue where the first digit could be missed if a user started dialing the transfer destination while the voice prompt was still playing. The system now correctly captures the full number even when dialing immediately.

Added a feature that allows selecting an account before token generation to make the configuration process clearer. SMTP authentication now supports both Basic Authentication and OAuth2. Basic Authentication is used when a password is provided, while OAuth2 is used when the password field is empty. Usage details are explained in the hint below the password control buttons.

SMS text block labels could appear across multiple ACD groups, and each group could display labels and text blocks from other groups. This behaviour has now been fixed so that each group only shows its own configured labels and text blocks.

The IMAP connector malfunction is triggered by the mailbox configuration used for IVR.

The email processing algorithms have been synchronized between the Portal and the IMAP connector to prevent unexpected errors caused by inconsistencies.

Sometimes deleting a service number could fail, this problem has been fixed.

Resolved an issue where ASR WAV recordings could not be downloaded from the call log. The root cause was that certain ASR IVR objects did not specify the ASR call recording name, causing the download to fail. The recording name is now correctly resolved in all cases, ensuring reliable access to ASR recordings from the call log.

Task Scheduler was evaluating all holiday lists in the system instead of only the one configured for the specific task causing scheduled jobs to not run on days that are holidays in unrelated lists.

This has been fixed.

Resolved an issue where emails in certain languages were sent with a blank subject line and empty message body due to special characters not being handled correctly. Emails now display their full content as expected.

Fixed empty Date / Time column in FTP Logs. Now The date and time of every log is displayed.

Improved handling of outbound calls when after-call routing is enabled. If the service number configuration is not suitable for this option, the call is now ended cleanly and the reason is shown in the call log.

Fixed a bug where picklist values in Teams Profile settings were not displayed correctly when editing entries with multiple selected values - some of the selected values would incorrectly appear in the "Available" column instead of the "Selected" column.

All selected values now appear correctly when editing a team profile.

Fixed an issue where the ACD-S-005 report could not be generated. The report contained a configuration error that prevented it from running. This has been corrected and the report now works as expected.

Resolved an issue where an agent's availability status was not correctly updated after completing a call transfer using an innovaphone hardphone. The agent now properly returns to an idle state after a successful transfer.

Fixed an issue where emails were not being routed correctly based on keywords. When keyword matching was set to search the email body, emails were incorrectly sent to the fallback route instead of being matched to the correct destination. This has been corrected and email keyword routing now works as expected.

The Export 2 button was missing from the Dialler Contacts view. Export 2 uses a specific export schema to define the column headers, unlike the standard export. This has now been corrected. The Export 2 button has been added, allowing users to export contacts with the correct column headings as defined by the export schema.

SMS sending via the LOX provider has been improved. Unicode SMS handling was corrected so that messages containing special characters or emojis are passed to LOX correctly. By default, is_unicode is set to true; in this mode, SMS messages may be sent in multiple parts due to provider/SMS length limitations. If is_unicode is disabled, messages may be sent as one SMS part when they fit the GSM character limit, but special characters and emojis may not be encoded or displayed correctly. The LOX send command now uses --data-binary for payload transmission and is configurable via the system parameter Portal.Daemon.SMS.Send.Lox24.Command, allowing easier adjustment without code changes. The is_unicode option is now configurable through the system parameter Portal.Daemon.SMS.Send.Lox24.InputFileContent.

Creating a callback event failed when no priority was set. This problem has been fixed. If no priority is configured in the IVR object, a default value of 50 is now used.

When exporting Lists via FTP, the column “Extra Data“ was not included.

This has been fixed.

The file name selection is implementd like Chrome / Windows / macOS do when downloading files.

1. Take base name + extension
2. If name is free → use it
3. If not → add (1)
4. If still not → try (2), (3), (4)...
5. Stop at first free name

Previously, SMS templates were not sorted, making it difficult to find specific entries. Now, SMS templates are sorted alphanumerically, allowing for easier navigation and selection.

Outbound calls from inactive service numbers are blocked. The system checks the selected number before dialing; if it’s inactive, it shows an error message and lets the agent select another service number.

In DiallerContactsHistory, unsuccessful dialler calls with the results busy, wrong number, and no answer created DiallerContactsHistoryID entries but no corresponding StatisticsPartAID, which led to incomplete reporting for these outcomes; this behavior has now been fixed so that StatisticsPartAID is correctly written for these cases

An issue was identified where, after performing a blind transfer using an Innovaphone device, the agent would incorrectly remain in a busy state and was not available for new calls. This has now been fixed, ensuring that agents are correctly set to available after completing a blind transfer via Innovaphone devices.