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 for spoken alarms to use. May be a combination of words and replaceable parameter tokens as chosen from the table in Alarm Message Templates:
Section: System
Default: AlarmSpeechTemplate = %A %W %M
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. To create a custom property value that will be dynamic and unique for each instance, use tokens. A token will be replaced by the meaning it represents. All non-token characters will be passed along as a string. (To pass a percent sign as part of a string you must type %%)
A custom template with a value of:
Check: %D%T - %A - %M
will output a message like:
"Check: [Date][Time] - [Area] - [Alarm description]"
You cannot pass an expression in the value field of a Context tag's custom property. To do this, you must create a custom tag type. See Alarm Notification Templates for more detailed instructions.
|
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
