ezeio2:userinterface:configuration:fields

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
ezeio2:userinterface:configuration:fields [2024-01-04 17:09] – [Configuring Fields] andrehezeio2:userinterface:configuration:fields [2024-01-04 17:11] (current) – [Configuring Fields] andreh
Line 50: Line 50:
 Enter nicknames or codes here, separated by a comma. These "Tags" are an alternate means of referencing one or more Fields and utilized in message templates, some dashboard Widgets and anywhere expressions are used (Fields,  alarms, alarm & restore actions, timers).  Enter nicknames or codes here, separated by a comma. These "Tags" are an alternate means of referencing one or more Fields and utilized in message templates, some dashboard Widgets and anywhere expressions are used (Fields,  alarms, alarm & restore actions, timers). 
  
-Tags names should always start with a letter, and only include letters, numbers, underscore (_) and hyphen (-). International or other special characters are not supported in tags. Avoid any other special characters and spaces.+Tags names should always start with a letter, and only include letters, numbers, underscore (_) and hyphen (-). Spaces, international letters or other special characters are not supported in tags.
  
 Asset tags can be user defined and/or generated by a device driver. They can be unique such as "HVACload" or generic such as "load". Asset tags should be kept short, starting with a letter, and containing no special characters or spaces. The asset tags are entered on the Field's configuration, for example as: HVACload  and referenced in an expression or message template as: <HVACload> Asset tags can be user defined and/or generated by a device driver. They can be unique such as "HVACload" or generic such as "load". Asset tags should be kept short, starting with a letter, and containing no special characters or spaces. The asset tags are entered on the Field's configuration, for example as: HVACload  and referenced in an expression or message template as: <HVACload>
  • ezeio2/userinterface/configuration/fields.txt
  • Last modified: 2024-01-04 17:11
  • by andreh