Endpoint tagging

Introduction

The goal of this feature is to allow dashboard definitions that can be used across multiple facilities, or even different clients, without the need to create independent copies. To achieve this, endpoint tags, or tags on the devices that contain them, are used to reference endpoints indirectly. The current option (reference to a specific endpoint) is maintained, and the ability to reference endpoints or groups of endpoints indirectly through tags is added.

The goal is to allow dashboard definitions that can be used across multiple facilities, or even different clients, without the need to create copies that involve additional effort and are then difficult to maintain.

Selecting an endpoint

To select an endpoint in a widget, the following methods are available:

• Individual endpoint selection (current method). In this case, a specific endpoint is chosen from the list, as is currently done. The widget is bound to the endpoint at dashboard design time, and will always refer to the specified endpoint. This type of selection must not be allowed in global dashboards.

• Indirect selection by tags (additional new method). In this case, a list of one or more tags is entered, and the chosen endpoint is determined at runtime on the back-end (when viewing the dashboard) based on the selected facility. The algorithm for choosing the endpoint to use is as follows:

1. First endpoint containing the specified tag, of the appropriate type, belonging to the current facility.
2. First endpoint containing the specified tag, of the appropriate type, belonging to any facility of the current client that the user has permission to access.
3. First endpoint containing the specified tag, of the appropriate type, belonging to any client that the user has permission to access.

NOTE: When "first endpoint" is mentioned in the paragraphs above, it refers to the first one meeting the condition, sorted by Endpoint ID.

Example

1. Dashboard 1 (any facility)

2. Widget 1 - Sensor containing the tag "temperature-sensor".

3. Widget 2 - Sensor containing the tag "humidity-sensor"

4. Widget 3 - Sensor containing the tag "people-counter"

   2. Then, in each facility, only the appropriate tags need to be assigned:

• Assign the tag "temperature-sensor" to the temperature sensors in all 3 facilities.
• Assign the tag "humidity-sensor" to the humidity sensors in all 3 facilities.
• Assign the tag "people-counter" to the people counters in all 3 facilities.

By implementing the dashboard this way, the same dashboard can be used in any facility, and the dashboard content will automatically adapt when switching from one facility to another. Additionally, if an endpoint is removed and replaced by another in any facility, the dashboard will continue to work normally as long as the new endpoint receives the appropriate tags.