A filter node limits what is in a dataset. This operation can:
It also contains additional logic for how the resulting dataset is sorted.
This step defines the base configuration for the filter.
This step contains logic to filter Attributes from a dataset. It affects the number of columns returned, and is equivalent to a “SELECT” statement in SQL. The user interface for this step is a list builder which builds a list of the attributes to return.
In EdgeSuite 3.0, this step will be pre-populated with all attributes in the dataset and a default type will be provided for all attributes that can be determined.
This step contains logic to filter records for a dataset. It affects the number of rows returned, and is equivalent to a WHERE clause in SQL. The user interface for this step contains an expression builder, which contains rules for evaluating values for specific attribute names. This accommodates both simple property comparison, as well as more advanced expressions. Refer to the sections below for more detailed examples.
A Static Property Comparison filters records based on values for a single attribute. For example, assume a dataset with event data, and assume end users are only interested in the critical events. The records need to be filtered by the values for a specific attribute name.
The resulting filter is shown below:
Notice that each rule has the same general pattern.
This type of filter checks values from multiple attributes using AND/OR operators. For example, assume a dataset with event data, and assume end users are interested in critical events for a specific AssetID. In this case, the records need to be filtered based on values contained in two different Attribute Names:
This step provides a way to cap the number of rows returned.
Row Limit = NO will return all rows.
This step defines how the resulting records should be sorted. The Sort user interface is a list builder control that supports multi-column sorting. The first item in the list represents the primary sort. Each additional attribute produces a sub-sort, based on its parents.
The example below will sort the resulting dataset by severity first. Records that have the same value for Severity_Name will then be sorted by “AssetID”.
Details about this step can found here: Satisfy Upstream Node Variables Wizard Step
This step provides a preview of the resulting dataset. It exposes upstream variables to test how inherited context changes will affect this result set.