Each event or alarm record includes a log code that defines the event type and actions associated with the event. The built-in event policies define inherent system behavior, such as which events are also alarms, and which events are recorded to the database (all built-in events are recorded to the database by default). These built-in policies are based on the log code only: no other criteria are used to define the event trigger.
The default event policies should be changed only if you need to change an inherent event behavior. For example:
· Whether the event is an alarm or an event.
· Whether the event is saved to the database.
· The event priority.
· The sound played when the event is triggered.
· The color shown for the event in the event modules.
When custom events are required, we recommend creating a custom event policy, as described in the following section.
See also: