Configuring the Litmus Production Record Tag Message Conversion Flow

to allow the flow to create the right message payload so that the data can be successfully ingested by litmus production record database using a litmus integration, there are two mandatory configurations the user has to make configure the topics for the tags to be used the purpose of the flow, is to ingest tag data collected by litmus edge as devicehub tags and modify the message payload to meet the requirements of litmus production record database for tag data the flow has to therefore subscribe to the topics of the tags which are to be send to litmus production record database the user provides these topics through the use of the litmus pallet node datahub subscribe by default the flow has one such node added, but customers can add more nodes as needed to provide a topic, users edit the datahub subscribe node and replace the placeholder "please enter topic" with the topic of a tag to be used by the event configuration and press the done button as typically more than one tag is required, users have several options for providing all the tags they require option 1 add more datahubsubscribe nodes the flow comes with a single datahub subscribe node in the section but users are able to add more nodes as they need and wire them all into the output the example shows how a user added more node by creating copies of the original node this option works well if a single devicehub device is to be monitored, but can become challenging to support if the flow is used to monitor multiple devices option 2 wildcards litmus edge allows users to make use of wildcards when providing a topic, so that one datahub subscribe node can be used to read more than one tag the flow is able to handle the use of wildcards this option has to be chosen carefully, as if several thousand tags are read, the flow can experience a slowdown example for a wildcard on a device level this option is very well suited if multiple devices are to be monitored but care has to be taken to the amount of tags the flow may subscribe too option 3 combination to make sure, that ideally only these tags configured in litmus production record database are read, the best approach is to combine both options this makes use of the ability of litmus edge, that different devicehub devices can have the same tag name for the same information for example the tag temperature or downtime can exist on several devices this means that the wildcards are used to read the same tag from all devices which have it but as each tag needs a data hub subscribe node, the user would add additional nodes accordingly configure the item and publishing topic for the modification of the message payload, the flow requires the tagitem to be provided which the value of the original payload represents more to the concept of tagitems for tags can be reviewed in the chapter core concept behind recording process and meta data for process tags docid\ amceahd6bo48cyboguikw by default the flow will use as tagitem "value" and as writetopic "litmus prorec" but users are able to modify these to modify the tagitem and/or writetopic, the user has to edit the sub flow this allows to set the desired values for these two settings and press the done button to start the processing, deploy the flow as it is possible to have more than one tagitem per devicehub tag or have different tagitems for different tags, users can add additional subflows final step after all configurations have been done and are deployed, it is recommended to setup a litmus integration using the db microsoft sql server connector how to setup an integration can be read up on using our litmus edge documentation after the integration is established, the user needs to subscribe to the topic which has been setup in the sub flow how a subscription for an integration is added, can be found in the litmus edge documentation add as local data topic the value used in your event configuration now, every time the flow publishes a new message on this topic, the integration will send it to litmus production record database