Filter Nodes
Route and direct messages based on various criteria without modifying them. Filter nodes typically
produce True/False outputs for boolean evaluations, or named connections for switch-style routing.
| Node | Description |
|---|---|
| Alarm status filter | Routes alarm messages based on their status (ACTIVE_UNACK, ACTIVE_ACK, CLEARED_UNACK, CLEARED_ACK, CLEARED) |
| Asset profile switch | Routes to a connection named after the originator asset’s profile |
| Check fields presence | Routes based on whether specified fields exist in message data or metadata |
| Check relation presence | Routes based on whether a relation exists between the originator and a target entity |
| Device profile switch | Routes to a connection named after the originator device’s profile |
| Entity type filter | Passes or blocks messages based on the originator entity type |
| Entity type switch | Routes to a connection named after the originator entity type |
| GPS geofencing filter | Routes based on whether GPS coordinates fall inside a configured geofence |
| Message type filter | Passes or blocks messages based on the message type |
| Message type switch | Routes to a connection named after the message type |
| Script | Routes using a boolean TBEL/JS function — True or False output |
| Switch | Routes to one or more connections returned by a TBEL/JS function |