Filter Node

Filters data based on specified criteria, allowing only data that meets certain conditions to pass through. This is useful for focusing on relevant data and reducing noise in the data stream.

What is a filter?

The filter serves a crucial role in data processing by controlling the flow of data based on specified criteria. Its primary purpose is to determine which data points are permitted to pass through the node, effectively filtering out any irrelevant or unwanted information. This selective process allows for more efficient data handling and ensures that subsequent nodes or processes only receive pertinent data. By employing a filter node, users can streamline their data pipelines, reduce noise, and enhance the accuracy and relevance of the insights derived from their IoT systems. This functionality is essential for optimizing performance and maintaining the integrity of data analytics within the platform.

Inputs

The filter node has a mandatory input which is:

Input	Requirement	Comments
Input Data Field	Mandatory	This is the field name within the incoming JSON payload that contains the data value.

Functionality

The filter node checks the incoming data for the input field name and it outputs the data based on the condition configured in the node.

Outputs

The filter node has an output only when the payload meets the condition configured in the node.

How to Use

Implementation

In the Rayven Workflow Builder:

Select Functions.
Drag the Filter node to the canvas.
Provide an input to the Filter node by connecting it to another node.
Double click on the Filter node to open the configuration window.

Configuration

Section: General
This section contains basic configuration elements required for any filter implementation
Field	Requirement	Comments
Node Name	Mandatory	Enter a name for this node. This provides a handle to which you and others can refer, so it should be simple but meaningful and explain the node’s purpose.
Input Field Name	Mandatory	Enter the field name exactly as it appears in the JSON.
Field Exists	Optional	This option will pass all of the JSON in which this field exists and will stop all those without it.
Condition	Optional	Another option is to choose a condition for the data to match in order to pass through this node; “=” in this case if this fields equals to a value or string then the case will operate, if not nothing will happen “>” in this case if this fields is larger than the value then the case will operate, if not nothing will happen “<” in this case if this fields is smaller than the value then the case will operate, if not nothing will happen “<>” in this case if this fields is different then a value or string then the case will operate, if not nothing will happen
Value	Optional	The value or string must match the field data to pass through according to the condition
Once In Time Period	Optional	Select from dropdown menu Seconds Minutes Hour Day Week Month It allows the first payload of the period to go through and block all others. You can choose a time period in which only the first JSON that will meet the criterias in the condition to be passed on.
Units	Optional	Enter an integer for the time period selected in “Once In Time Period”. Example: To configure 1 hour Once In Time Period must be set to “Hour” Units must be set to “1”