The date format supports an optional day shift[<simpledateformat>|<day shift>]. Example:ACDGroupsReport3[yyyy-MM-dd_HHmmss|-1].pdfgenerates a file using yesterday’s date.
Salesforce: Support for External Client Apps (ECA) and OAuth Client Credentials Flow
Salesforce announced that starting withSpring ’26, the creation of newConnected Appswill be restricted. Integrations must useExternal Client Apps (ECA)instead.
The Salesforce integration in the jtel portal has been updated to support authentication via theOAuth 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 theClient IDandClient Secret, and the fieldsUsername,Password, andSecurity Tokenare no longer required.
Existing integrations using Connected Apps and username/password authentication continue to be supported.
The Salesforce documentation has been updated accordingly.
Extension of Daily Cleaner for Customer-Specific Procedures
The daily database cleaner has been extended to support customer-specific cleanup procedures.
A new parameterPortal.Cleaner.CustomProcedureshas been introduced. It allows defining acomma-separated listof customer-specific cleanup procedures that will be executed automatically as part of the daily cleaning process.
Dialler Contacts - Export all contacts in CSV format.
A newExportbutton has been added to theDialler Contactsview. Users can now exportall dialler contacts(across all campaigns) inCSV formatdirectly from the Dialler Contacts screen.
This allows an easy and fast full-contact download without needing to export per campaign.
ACD Events - Improved handling of ACD media events
ACD media event handling has been improved to make working with new events faster and more convenient.
When the new settingAcdEvents.OpenNextNotOpenedEventis 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 settingAcdEvents.OpenCrmUrlOnOpenEventis 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.
The new functionality allows the Portal to trigger actions in the MiniClient application installed on the user’s PC
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:
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
*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>
A newAgent Labelfield 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:
New outlook has limited or no native support for opening .eml files, unlike classic Outlook.
Introduced a new boolean user propertyAcdAgent.MediaEvent.Email.Download.AsMsgin Portal GUI. When enabled (true), emails are downloaded in.msgformat instead of.eml, where available. This feature requires IMAP Connector version3.1 or higher.
A new configuration parameterMsgAnswerDetectionAlgorithmhas 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.msgfile:
Subject: the token is added to the email subject
Body: the token is embedded in the email body (hidden)
REST - Problem when deleting dialler contacts with same user data.
When batch deleting dialler contacts via the REST endpoint/dialler/contactsusingUserDataList, 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.
Confluence - SMS text block labels displayed across multiple ACD groups
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 email processing algorithms synchronized in Portal and IMAP connector
The email processing algorithms have been synchronized between the Portal and the IMAP connector to prevent unexpected errors caused by inconsistencies.
Innovaphone - Agent Remains Busy After Blind Transfer via Innovaphone Device
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.