Alarm Notification Templates and DialerLocation have been moved from Settings.Dynamic to the default languages file (en.csv). To find a template phrase in the Languages panel of the Application Properties dialog, use the View button to display the Key column. Template phrases use the original property names as keys.
You may still use these properties in [System] section of your Settings.Dynamic file, but you must insert them using the Advanced mode of the Edit Properties dialog. The property will take precedence over the phrase in the language file.
Alternatively, you may create localized template values as properties of a parent Context tag.
Provides a template to use for alarms delivered to an email address via the Alarm Notification System. May be a combination of words and replaceable parameter tokens as chosen from the table in Alarm Message Templates:
Section: System
Default: AlarmEmailTemplate = %D %T%NArea: %A%NName: %F%NDesc: %M%N%L
Context (Site) Tags and Alarm Notification
Context tags (or custom types derived from a Context tag) may define custom alarm message templates, for use by all alarms occurring within the structure. This is done by adding the desired template name(s) to the Context's list of properties. If doing so, it is typical to use an expression when defining the template so that the message will be unique for each instance of the type.
For example, Concat(\Name, "%N%M") would show the name of the Context tag plus the description of the alarm (which may be a child, grandchild, etc. of the context).
Because tag names and other properties may contain characters that would conflict with template characters, such as percent signs (%), you should always process information from the Context tag using the \PrepStringForTemplate() function. Updating the previous example, Concat(\PrepStringForTemplate(\Name), "%N%M") is the safer way to reference \Name in case any given name contains a %.
Note that you might also need to use a \GetPhrase or \GetParmPhrase call in your expression. See: Multilingual Expressions
|
Token |
Meaning |
|---|---|
|
%A |
Area of the Alarm tag. |
| %C |
Custom data provided by the application. (See following notes.) |
|
%D |
Date of the alarm |
| %F | Full tag name |
| %H | Short tag name |
| %K |
Station number (Part of every Polling driver, and Station type. Context tags used as site must be given a property named "Stn", in which the station number may be stored.) |
| %L |
Opt-out message. This is be used only with SMS and EMail templates The message is stored with the language phrase key AlarmOptOutMsg and defaults to: |
|
%M |
Alarm description |
|
%N |
New sentence for email and pager messages. |
| %O | Operator |
|
%P |
Priority of the alarm. |
| %S | Status of the alarm |
|
%T |
Time of the alarm |
|
%U |
Units of the Triggering tag. |
|
%V |
Alarm value (this is the value of the alarm trigger at the time that it triggered the alarm) |
|
%W |
Pause for ¼ second. Has no effect on email or pager messages. |
| %Z | Setpoint. |
Value (%V) and Setpoint (%Z) will use the labels corresponding to these values as stored in the record where applicable. If no labels can be found, the raw numbers will be used.
The %C token in a template can only obtain numeric and text values, not complex values. If a numeric or string value that exists inside a complex value needs to be included in an alarm notification, an AlarmTemplateHookC module will need to be created that returns this value.
The Custom field can be set in a variety of ways:
- In the Commission() call via the Custom field of the Alarm Configuration record.
- In the EvaluateAlarm() call via the Custom parameter
- In any Alarm<Action>Hook module by setting the Custom field of the TransactionInfo structure.
Alarm Message Templates - Look here for examples
