Universal Devices ISY-994i Series, Руководство пользователя

Страница: 155 / 692

Page | 132
8.4 Email Substitution Variables
17
Note: In case of email customized content, both the Subject and the Body must be non-
empty otherwise, emails shall not be sent!
8.4.1
Substitution Variables
•
Custom Email definitions are available in the Admin Console by going to
the
Configuration / Emails/Notifications / Customizations tab
•
Substitution variables are available inside custom email definitions in the
form
${ <variable name> } .
•
Substitutions can be manually made in the body, URL or header of Network Resources
from version 4.3.26. If you included them in the URL then you cannot use the 'Encode
URL' option
•
In most cases, these variables use the ID of the element being referenced
•
For example ${sys.node.11 22 AA 1.name} would use the name of the device node
whose address is 11 22 AA 1
•
Instead of specifying a fixed address, the special character # may be used to
reference the element in the event that caused the program to run. (Does not work
in network resources)
•
For example, if a status event for node 11 22 AA 1 caused a program to run,
then ${sys.node.#.name} would use 11 22 AA 1 as the address.
•
If a variable has more than one ID then any combination of fixed addresses
and
# is valid. For example, the following are all valid
•
${elk.keypad.1.key.1.led} -- Show LED status of F1 Key on Keypad 1
•
${elk.keypad.#.key.#.led} -- Show LED status of event Key on event Keypad
•
${elk.keypad.#.key.3.led} -- Show LED status of F3 Key on event Keypad
•
${elk.keypad.1.key.#.led} -- Show LED status of event Key on Keypad 1
•
User defined Integer and State variables are referenced with their type (1-Integer,
2-State) and ID Number for example: ${var.2.3} for the state variable with ID # 3
17 (Universal Devices)