Interlogix TruPortal User Manual
Page 72
Configuring the System
60
TruPortal Software User Guide
•
Up to 10 actions can be included per action trigger record. These actions can be any combination
of activation and/or deactivation actions.
•
Actions can be configured to occur when a trigger is deactivated.
•
Use the Status field on the top of the System Administration > Action Triggers page to enable or
disable action trigger records.
•
Action triggers can be executed manually on the Monitoring > Action Triggers page. See
Note:
To provide a quick way to secure all doors in a facility, create an action trigger record to
lock all doors, and then trigger it manually on the Monitoring > Action Triggers page
when necessary.
•
Disabled inputs and outputs can be included as an action, but they will have not be implemented
until the input or output is enabled.
•
Action triggers, schedules, and manual control can all impact the state of devices and are treated
equally by the System. The last operation executed determines the state of a device.
•
Action triggers do not override the global “Lockout All Doors” or “Unlock All Doors” door
states.
•
If an entity (for example, a reader) is defined in an action trigger record and then the entity is
deleted from the System, all corresponding action trigger records will also be deleted. If the
entity is recreated, new action trigger records can be created for the entity.
•
If the System is configured to send automated emails, an action trigger record can be created to
send a notification to an email list when a trigger condition changes. Email delivery will be
attempted for the selected Retry Limit duration relative to when the action was triggered.
•
IPSDCs do not support Buzzer On and Buzzer Off actions.
•
If an action trigger is directed to an entity whose parent module is offline, the action will have no
effect on that entity when the module comes back online. In other words, actions are not persisted
or queued.
•
Output actions will not log an Output On or Output Off event unless the output physically
changes state. For example, if an output is on and action trigger occurs to turn that output on,
there will be no Output On event generated.
In addition, note that trigger conditions are assumed to be in an indeterminate state and will transition
to either true or false to execute the corresponding actions:
•
For all records when the System starts up.
•
For each record when a record is configured and saved.
•
For affected records when a referenced entity is deleted.