Note: When you disable an alarm using the alarm list, the action is considered an operational change (as opposed to a configuration change). In other words, you may perform such an action while bypassing the VTS locking scheme. The change will immediately be propagated to all workstations running the application, regardless as to whether the application's primary configuration server is present or not. Information on operational and configuration changes is provided in Operational Changes vs. Configuration Changes ".

Note: Users must have the Alarm Disable system privilege granted to their user account to be able to disable alarms in this fashion. Information on system privileges can be found in Alarm Disable Privilege.