BFormat default scripts

The system populates the text properties of some components (copied from palettes or originated from manager views) with default BFormat scripts. Other text properties default to empty.

This table lists examples of the components with default scripts.

Table 1. Default BFormat scripts for a few properties
Component	Property	Default Script	Notes
Alarm extension for points, e.g. OutOfRangeExt, etc.	sourceName	`%parent.displayName%`	Suitable as is in many cases, such as 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 work with these default values.
Any device-level component’s AlarmSourceInfo slot.	sourceName	`%parent.parent.displayName% %parent.displayName%`	Often both properties work with these default values.
EmailRecipient	subject	`%alarmData.sourceName%`	The system provides much additional alarm data in the slot that contains the body of the email.

For a property value you can enter multiple BFormat scripts along with static text, as demonstrated by the defaults for a device’s AlarmSourceInfo (sourceName) property in the table. 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 BFormat script (%alarmData.sourceName%).

BFormat scripts can save time by enabling the replication of applications, where you can achieve the desired result with minimal custom edits to property values. You may still custom format specific text as needed.