Alert macros for alert action settings on NetBotz

[EcoStruxureIT]

Alert macros are available for use when defining alert action settings on NetBotz Appliances.

Macro	Example	Definition
${ALERT_LEVEL}	First Alert Level, Second Alert Level	Corresponds with the Label value of the alert sequence.
${ALERT_PROFILE}	Default, Profile #1	The name of the specific alert sequence that caused the alert to be generated.
${ALERTPODSERIAL}	NB007100730114	The serial number of the pod that either contains the sensor that reported the alert or to which the sensor is connected.
${ALERTPOD}	My Pod	The label of value of the pod that either contains the sensor that reported the alert or to which the sensor is connected.
${ALERTPORT}	Ext1	The label value for the external sensor port to which the external sensor that reported the alert is connected.
${ALERTSEV}	ERR, WARN-RTN	The severity value reported by the sensor that is generating the alert (such as ERR, WARN, INFO). If the alert state has returned to normal, the severity value will be followed by "-RTN" (for example WARN-RTN).
${ALERTTIME}	4/2/2009 13:01	The date and time at which the alert notification was generated.
${ALERTTYPE}	HIGHERR	The type of alert.
${CURRENT_ALERT_NUM}	0, 1, 2	The number of times the alert sequence has been repeated, from 0 up to the Repeats value for the alert sequence.
${EVENTID}	3E4512C0FE03440F	The unique 16 character identifier shared by all messages generated as a result of a single alert notification event. For example, if an appliance generates an alert notification when the internal temperature sensor threshold is exceeded, and then generates a "return to normal" message when the temperature drops below the high threshold, both of these messages will have the same Event ID number. However, if the temperature rises again and a second threshold exceeded alert is generated, the second alert will have a new Event ID.
${ISACTIVE?yes?no}	“active” and “cleared”	Specifies custom active vs. return to normal text. The strings “yes” and “no” can be replaced with user-specified strings. For example, if you specify “active” and “cleared” for the “yes” and “no” values and the macro is translated, if the alert is still active the word "active" would appear and when it has returned to normal, the word "cleared" would appear.
${RESOLVE_TIME}	13:07:13	The time at which the alert condition returned to normal.
${RESOLVECOMMENT}	“Turned on the A/C”; “Fixed the leak”	The text entered into the user-specified description field whenever an alert needs to be manually returned to normal (an option which can be selected whenever a threshold is configured).
${RESOLVEUSERID}	joeuser	The user ID that is responsible for manually resolving an alert (when this option applies).
${SENSORGUID}	B000113_TEMP1	The globally unique ID of the sensor generating the alert.
${SENSORLUID}	TEMP1	The locally unique ID of the sensor generating the alert.
${SENSORNAME}	Bldg. 3 Door	The name of the sensor associated with the alert.
${SENSORTYPE}	TEMP	The type of sensor generating the alert.
${SENSORVAL}	60	The value reported by the sensor that is generating the alert.
${START_TIME}	13:01:45	The time at which the alert condition was initially detected.
${USERDESC}	“Too high”	The user-specified description value which can be defined within the threshold configuration.
${USERURL}	http://www.mysite.com	The user-specified URL that can be defined within the threshold configuration.