A client filter reduces the number of records displayed in a Visualization. It does not affect what gets returned from the server. To limit records returned from the server, administrators use variables inside of queries, which ultimately get displayed as Page Variables. Client filters are a separate concept, and act as a second layer of filtering. The two concepts are visually separated within the product as well. Server filters show up as Page Variables while client filters are displayed on the individual Visualizations they affect.
Client filters can be used in conjunction with server filters. The server filter is always applied first, limiting what is returned from the server. The client filter then runs against that result set, allowing it to be filtered again. It is important to keep this relationship in mind, because it can be easy for a server and client filter to fight with one another.
Currently, client filters only work with tabular datasets. Client filters will not show up as options for relational Visualizations like Topology and Flow Diagrams.
To create a client filter, perform the following steps:
edgeSuite ships with several different types of client filters.
Limits records by a configured number of rows, and allows an end user to “page” through the results.
Limits records by a custom expression which can compare values in multiple attributes.
User-applied filters for a Visualization can be persisted during a session, across the user’s sessions on the same browser, or none at all. The behavior can be managed by setting the edge property key: client.filter.persistentStrategy to one of the following values:
This was the behavior before version 3.8.4. Every visit to the same page starts with no filter setting set.
Filter setting for each Visualization is persisted during the duration of the user’s session. This is the default behavior.