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)

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.

This allows an easy and fast full-contact download without needing to export per campaign.

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.

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.