Litmus Production Record Event Processing Flow
Litmus Production Record Database allows for two ways of monitoring production event triggers and recording the respective production record data.
As shown in the use cases:
the first option is to make use of the option to define single trigger based event monitoring inside Litmus Production Record Database itself. Where raw process data for tags are send to Litmus Production Record Database and used both for trigger monitoring as well as providing the data for the production event record.
If triggers require the monitoring of more than one tag and/or the trigger is also used for additional task not related to Litmus Production Record Database, the event monitoring has to be done outside of Litmus Production Record Database such as Litmus Flows.
An example for this is described by the use case:
If a the user has deployed Litmus Edge, the recommended approach is to make use of Litmus Flows for the event monitoring. To allow users to not have to spend time developing such a flow, Litmus offers the solution Litmus Production Record Event Processing Flow .
The biggest advantage of this flow is, that it scales very well allowing to monitor the same event for different devices. As it tracks events based on the name of a DeviceHub device. Therefore, if several devices have the same tags holding the same information, they all can be processed by the same flow.
After having purchased the solution from the Litmus Central Portal solutions catalogue, the user will have the file name Litmus_Production_Record_Event_Processing_V1.0.0.json.
This file can then be imported to a Litmus Edge Flows Instance.
After successfully importing and deploying the flow into the Litmus Flows instance, the user is ready to take the next step Configuring the Litmus Production Record Event Processing Flow.