As copied from palettes or originated from “manager” views, some components already have default values in certain BFormat-type properties (while others may default as empty). A few examples of those components with default values are listed in Table 1.
Table 1. Default values for a few properties using Format data type
| Component | Property | Default Value | Notes |
|---|---|---|---|
| Alarm extension for points, e.g. OutOfRangeExt, etc. | sourceName | %parent.displayName% | Suitable “as is” in many cases, for example where all parent points are uniquely named. |
| History extension for points, e.g. NumericInterval, etc. | historyName | %parent.name% | |
| Any network component’s AlarmSourceInfo slot. | sourceName | %parent.displayName% | Often both properties are left at default values. |
| Any device-level component’s AlarmSourceInfo slot. | sourceName | %parent.parent.displayName% %parent.displayName% | |
| EmailRecipient | subject | Niagara Alarm From %alarmData.sourceName% | Much additional alarm data is used in the “body” slot. |
Note that in the property value, you can use multiples of scripted variables along with “static text,” as done in defaults for a device’s AlarmSourceInfo “sourceName” property
(a static space character separates the
“%parent.parent.displayName%” from “%parent.displayName%”. The subject property of the EmailRecipient contains static text "Niagara Alarm From " ahead of the variable.
Copyright © 2000-2014 Tridium Inc. All rights reserved.