Transformation Nodes
|
ThingsBoard PE Feature Only ThingsBoard Professional Edition supports PE Transformation Nodes feature. See ThingsBoard PE Installation Options to install ThingsBoard PE. |
Transformation Nodes that are specific to ThingsBoard PE. Used for changing incoming Message fields like Originator, Message Type, Payload and Metadata.
Duplicate To Group Node
| Since TB Version 2.1 |
Duplicates message to all entities belonging to specific Entity Group.
Entities are fetched from Entity Group detected according to the configuration.
Entity Group can be specified directly or can be message originator entity itself.
For each entity from group new message is created with entity as originator and message parameters copied from original message.
Configuration:
- Entity group is message originator - if set, message originator will be considered as Entity Group used to fetch entities. In this case incoming message will be routed via Failure chain if message originator type is not Entity Group.
- Target entity group - specific target Entity Group used to fetch entities.
New messages will be duplicated to group entities and forwarded via Success chain if target Entity Group is detected successfully and contains at least one entity. Otherwise original message will be forwarded via Failure chain.
Duplicate To Related Node
| Since TB Version 2.1 |
Duplicates message to related entities fetched by relation query.
Related Entities found using configured relation direction and Relation Type.
For each found related entity new message is created with related entity as originator and message parameters copied from original message.
Configuration:
- Relations query - query used to find new entities starting from incoming message originator. In ‘Relations query’ configuration Administrator can select required Direction and relation depth level. Also set of Relation filters can be configured with required Relation type and Entity Types.
New messages will be duplicated to found entities and forwarded via Success chain if at least one entity will be found using Relations Query. Otherwise original message will be forwarded via Failure chain.