Tag rules

Standard

Rules for the choice value tags are automatically generated based on the choice values found in the defs.json file. Another set of rules is automatically generated based on the def type inheritance tree in Haystack 4.

For example, water is a subtype of liquid, which is a subtype of fluid, which is a subtype of substance, which is a subtype of phenomenon. As a result, there is a tag rule that implies the liquid tag if a component has the water tag, or a tag rule that implies the fluid tag if a component has the liquid tag (direct or implied).

Custom

The Niagara configuration file defines tag rules that unlock some tagging convenience features in the framework. There are rules that imply simple tags based on the component’s type such as the point tag on BControlPoints and the bacnet tag on BBacnetNetworks. There are rules implying smart tags that derive their value from something else such as the unit tag whose value is based on the component’s units facet. An alternate configuration file can be specified if you wish a different set of tag rules and/or if you want to change the tag types they imply.