...
Users can add in their own CSS and Classes by following this guide: /wiki/spaces/FINFrameworkV101/pages/772803323Adding CSS to Graphic
A list of available Graphic Builder Classes: /wiki/spaces/FINFrameworkV101/pages/772802474GB Classes
Basic
In the 'Basic' section you will also find most basic properties that are available to that component such as:
...
When a point is brought in "Absolute by Point id" the path is automatically hardcoded to get data from that exact point no matter where the graphic is loaded. An example of a Room Temp's point s point binding, that was brought in 'Absolute by Point Id', will be as follows: id==@1eeaf884-82cd6356 . So if this same graphic is loaded on any other equipment it will always reference that exact specific point (id) in the database and load up that specific points data.
...
- Relative: By Tag points will have an equipRef and multiple tags
Relative By Tags makes it so that the points are relative based on their current tags. When points are relative, they are not "Hardcoded" to one set of equipment's data, they are relative and will load on any equipment that has similar points based on the points tags. An example of a Room Temp's point s point binding, that was brought in 'Relative By Tags', will be as follows: equipRef=$self and air and temp and point and zone . So if this same graphic is loaded on any VAV it will look for a point that has those same exact tags, and use that as the path to load up the points data.Relative By Tags is recommended for situations when your database has points from several similar equipments that do not share the same navName. This is common when using different brands where point names don't match. Instead of having to worry about each point having the same exact name, you can have them be relative by tags instead. NOT recommended for a server that is still being worked on where tags will be changing often.
...
Relative - By navName: This makes it so that the points automatically come in Relative, based on their current navName. When points are relative, they are not "Hardcoded" to one set of equipment's data, they are relative and will load on any equipment that has similar points based on the points navName. An example of a Room Temp's point s point binding, that was brought in 'Relative By navName', will be as follows: equipRef=$self and navName=="Room Temp" . So if this same graphic is loaded on any other equipment it will look for a point that has that same exact navName and use that as the path to load up the points data.
...