Skip to main content

Ver. 11.5.0.10 Maintenance Release Notes

Maintenance Release 11.5.0.10 for DeskAlerts resolves major issues impacting alert delivery and system performance, including preventing blank alerts during high server load, optimizing Azure AD sync for large audiences, and enhancing reconnection mechanisms for consistent alert and survey delivery. Additionally, issues with stopped alerts being delivered and incorrect recipient statistics have been addressed.

Updating both the server and agent applications to version 11.5.0.10 is required to implement these fixes and ensure system reliability.

Enhancement​

  • Sender Display Name for SMTP integration settings
  • Added the ability to set the sender's Display Name in SMTP integration settings, allowing email alert recipients to see a customized sender name.

Resolved Issues​

  • Alerts appeared as a white screen during extreme server loads. Alerts are now downloaded and verified before being displayed, preventing this issue.
  • Server crashes occurred when broadcasting content to audiences of over 15,000 users due to unbalanced load distribution among connection services. As a result, some connection services got overloaded with connection requests from the agent apps. A maximum connection cap was introduced for connection services to prevent occurrence of such scenarios.
  • Optimized Azure AD Sync process, which previously completed successfully but resulted in 0 objects being added to the audience if the tenant contained over 15,000 objects.
  • [Intermittent] Alerts and surveys were delivered twice to some machines due to a loss of the first delivery confirmation caused by the communication interruption between the main and connection services.
  • When the main service was not responding to a connection service for over one minute, the connection service switched to "Disconnected" mode. Enhanced a reconnection mechanism to ensure continuous and reliable connectivity between DeskAlerts main and connection services.
  • [Intermittent] Some surveys were delivered only after restarting the connection service. Enhanced a reconnection mechanism to ensure continuous and reliable connectivity between DeskAlerts connection and the main services.
  • Logging details of all AD/Azure AD sync events caused database performance bottle necks.
  • Stopped scheduled alerts appeared in the History section of the agent app.
  • Stopped scheduled alerts were delivered to the audience after an agent app reconnected to a server.
  • Stopping alerts targeting recipients by IP addresses or IP address ranges did not work as intended, causing stopped alerts to be delivered to the audience.
  • [Intermittent] A "Can’t connect to client service" error appeared on some machines when stopping a lockscreen due to a failed update of the lockscreen service.
  • In version 11.5.0.9, scheduled alerts with additional channels (email, SMS, and text-to-call) were only delivered to the agent application and not to the additional channels.
  • Pop-up alert acknowledgement statistics only displayed the first 20 users when switching to subsequent pages.
  • When the "acknowledgement" setting was enabled in default alert settings, RSVP alerts were sent with "Acknowledge" and "Postpone" buttons, which are not part of the RSVP module functionality.
  • Free text answer option remains visible to the audience in cloned RSVP alerts, even after being disabled in the alert settings.
  • Deleted users and their agent apps were displayed in dashboard widgets as users with active accounts.
  • Emergency alerts appeared in the Pop-up Alerts list with the creation date of the Emergency Alert template instead of the actual emergency alert send date.
  • Users, groups, and domains were not imported via CSV files.

Known Issues​

  • [Intermittent] The DeskAlerts agent app may intermittently display outdated or missing response statistics after completing a quiz or poll. This occurs due to delayed server responses.