Skip to main content

Ver. 11.5.0.7 Maintenance Release Notes

We’re releasing ver. 11.5.0.7 for DeskAlerts, focusing on key improvements and fixes. This update enhances email alerts with embedded images, improves AD sync performance, and introduces new Arabic fonts. Several issues affecting alerts, UI stability, and reporting have also been resolved.

We recommend updating both server and client components to version 11.5.0.7 for optimal performance.

Improvements

  • Email Alerts with Embedded Images: Email alerts can now include images embedded directly within the HTML page, enhancing the visual presentation of email alerts.
  • Enhanced Personalization Feature: The Personalization feature has been improved to support attributes for both the sender and the recipient of an alert. These attributes now include First Name, Last Name, Display Name, Email, and Phone Number. Previously, these attributes were only available for recipients.
  • New Arabic Fonts: We have added several Arabic fonts, including Al-Jazeera Arabic (Regular, Bold), Royal Arabic, and The Sans Arabic (Light, Regular, Bold, Black), providing more customization options for alerts in Arabic.
  • Optimized AD Synchronization: The performance of Active Directory synchronization has been significantly improved, resulting in a 4x faster sync for large domains.

Resolved Issues

  • An emergency alert using the attribute #UserFirstName# displayed the recipient's information instead of the sender's.
  • The scrollbar in the audience search for sending content did not appear when there were additional results available.
  • [Intermittent] A "503 Service Unavailable" error appeared in alerts when the server was busy at the time the alert was received.
  • CSV/XLSX reports for recurring alerts only included information for the most recent alert in the series, instead of cumulative data.
  • If the connection was lost for 3 hours or more, the Mac agent remained in a "Reconnecting" status indefinitely.
  • Alerts were not displaying on the main screen of Windows.
  • The "Postpone" option was shown in alert and emergency alert previews, even when disabled in the alert settings.
  • A "500.37" error message appeared after an on-premises deployment when attempting to open a dashboard URL due to a failed connection to the Azure SQL PaaS database.
  • Skin lists did not display all available skins for a publisher.
  • Preview functions for RSVP, Survey, Quiz, and Poll were not working in the Arabic language.
  • The password change timestamp for publishers did not match the device time.
  • The sync start time did not match the device time.
  • Simple AD registration in the desktop agent failed with a "Value cannot be null" error due to an incorrect encryption key.
  • Changed registry type from REG_SZ to REG_RWORD in the NoChangingLockScreen field, which improved the stability of lock screen configuration.
  • The license trend chart widget was difficult to read due to overlapping digits.
  • Start, stop, and delete alert actions failed when the agent was in a "Disconnected" state.
  • Users from individual Organizational Units (OUs) were not syncing until the entire domain sync was completed.
  • The "Fullscreen" option was not applied to Emergency alerts, RSVP, and Surveys created from templates that had this option enabled.
  • In the mobile app, the QR code reader failed to scan the server QR code, requiring manual input of the server URL.
  • Lock screens sent to devices were not being applied or stopped due to improper DeskAlerts Client Service functionality.
  • Each click on "Acknowledge" in an alert and scrolling of the ticker was counted as a separate acknowledgment in statistics.
  • A blank scrolling ticker and the error "The request was canceled due to the configured HttpClient.Timeout of 600 seconds elapsing" occurred due to an outdated token.
  • The alert send time in CSV/XLSX reports did not align with the publisher's browser time.
  • A "Forbidden" error was shown in a received blank alert due to missing cookies.
  • Synchronization of large Active Directories was halted due to enabled Trace and Debug logs causing an error.
  • QR code reader in DeskAlerts 11 Mobile App did not scan server information during user authentication.