•Fixed a bug when closing the Domain or deactivating the Alarm Server, which eventually lead to losing some alarm messages (up to 99) that had not been recorded in the database yet. For more information, please refer to https://kb.elipse.com.br/bug0010182-some-alarms-may-not-be-recorded-in-the-database/. This bug occurs since v1.18.147 (or earlier).

•Fixed a bug that could cause Viewer script errors after Deactivate method call, in reference to an Alarm Server object. For more information, please refer to https://kb.elipse.com.br/bug0010183-error-in-a-viewers-script-after-alarmservers-deactivate-method-has-been-called/. This bug occurs since v1.21.96.

•Fixed Alarm Summary's behavior when the Domain stops. Previously, the Summary was erased whenever the Domain stopped (without closing it). Now, Summary messages are only erased if the Domain is closed. For more information, please refer to https://kb.elipse.com.br/bug0010196-alarm-messages-are-removed-from-e3alarm-when-domain-stops/. This bug occurs since v1.21.96.

•Now, when deactivating and then reactivating the Alarm Server at run time, the Alarm Summary hides (when deactivating) and reappears (when reactivating). No message is logged to the database during this process. For more information, please refer to https://kb.elipse.com.br/bug0008263-apos-a-desativacao-do-objeto-alarmserver-o-objeto-e3alarms-nao-mostra-mais-nenhum-alarme/. This bug occurs since v1.18.147.

•Fixed E3 Alarm's behavior, which allowed an alarm message to remain active in the Summary if the related Alarm Source was disabled (AlarmVerify = False) via Studio, and later the Domain was updated. Now,when updating the Domain, this message is removed from the Summary, and a message with Enabled = 0 is logged to the database. For more information, please refer to https://kb.elipse.com.br/bug0010260-alarm-message-remains-in-the-summary-if-alarmsource-is-disabled-in-e3-studio/. This bug occurs since v1.21.96.

•Now alarms are only checked after Alarm Config's complete activation, which happens after the execution of OnStartRunning scripts and Link creation. This allows alarms to be completely reconfigured during application activation (or during some object's reactivation via Activate method), which includes renaming areas, enabling or disabling alarm acknowledgment, changing verification limits, etc. For more information, please refer to https://kb.elipse.com.br/bug0002873-areas-name-cannot-be-changed-at-runtime/. This bug occurs since v1.20.242.

•The alarm's acknowledgment status is no longer lost when the Alarm Source restarts (either by refreshing the Domain, or by using Deactivate or Activate commands). For more information, please refer to https://kb.elipse.com.br/bug0009880-active-alarms-need-to-be-reacknowledged-when-domain-is-updated/. This bug occurs since v1.21.96.