Alarm requirements for InTouch client applications
- Last UpdatedJul 16, 2024
- 2 minute read
For Application Server alarming to function, the following conditions must be met:
In Application Server:
-
One or more Area objects are deployed and running.
-
The source object is on scan.
-
The source object’s Area is on scan.
-
Alarming must be enabled for the target object.
-
An InTouch alarm provider on any WinPlatform in the Galaxy.
In InTouch:
-
The InTouch client application is running in WindowViewer.
-
An InTouch alarm ActiveX control is placed in a window and configured as an alarm consumer for the Galaxy.
-
The user has logged into InTouch with security enabled and is authorized to acknowledge alarms for the object that is in the alarm state. If the user only wants to view alarms, security authorization is not required.
Application Server validates the user has sufficient security privileges to acknowledge the alarm.
If the user does not have privileges to acknowledge alarms, the user can attempt to acknowledge the alarm, but the Galaxy rejects the acknowledgment request.The alarm remains unacknowledged in the InTouch Alarm display.
The rejected alarm acknowledge event is recorded in InTouch Event History if the user attempting the acknowledgement has a valid Galaxy user account. Otherwise, the rejected acknowledgement is not recorded as an event.
You can acknowledge multiple alarms by providing a valid signature. At runtime, the Industrial Graphics SignedAlarmAck() script function checks a set of alarms and conditions to find out if any alarm from the list requires a signature in order to acknowledge it. If so, you must provide your user name, password and domain or your Smart Card details and PIN to authenticate yourself and acknowledge the alarms. To be able to provide the Smart Card details, your computer must be configured for Smart Card authentication.
Note: Smart Card authentication is not supported in multi-galaxy environments for read/write operations to remote galaxies.
If even one alarm in the list requires a signature, you must provide a signature to acknowledge the alarms. The SignedAlarmAck() function will acknowledge ALL the alarms in the list.
With the SignedAlarmAck( ) function, you can provide credentials and acknowledge an alarm or group of alarms even if you are not the logged-on operator.