HiveMQ Edge is an MQTT gateway that enables interoperability between OT devices and IT systems. It translates diverse protocols into MQTT for streamlined communication and helps organize data into a unified namespace, making managing and streaming data across your infrastructure easier.
The PR adds support for user to edit the unique id of several types of nodes in the Designer
Data Policy nodes
Behaviour Policy nodes
Operation nodes
It dissociates the id of the ReactFlow node (uuid) from the user-facing id of the policy element. In effect, it acts as a name for the elements.
The id is mandatory and editable in the relevant side panel and serialised with the policies. They are bound to a uniqueness check, based on the type:
Data Policy id must be unique among all published data policies
Behaviour Policy id must be unique among all published behaviour policies
Operation id must be unique among the operations connected upstream in the given pipeline (i.e. it must not be used BEFORE in the pipeline but MIGHT be used in another pipeline of the same policy)
The main effect of the change is that policies are now listed with a more user-friendly name in the landing tables.
See https://hivemq.kanbanize.com/ctrl_board/57/cards/19466/details/
The PR adds support for user to edit the unique
id
of several types of nodes in the DesignerData Policy
nodesBehaviour Policy
nodesOperation
nodesIt dissociates the
id
of the ReactFlow node (uuid
) from the user-facingid
of the policy element. In effect, it acts as a name for the elements.The
id
is mandatory and editable in the relevant side panel and serialised with the policies. They are bound to a uniqueness check, based on the type:id
must be unique among all published data policiesid
must be unique among all published behaviour policiesid
must be unique among the operations connected upstream in the given pipeline (i.e. it must not be used BEFORE in the pipeline but MIGHT be used in another pipeline of the same policy)The main effect of the change is that policies are now listed with a more user-friendly name in the landing tables.
Out-of-scope
Before
After