Applies to: Insight 4.3.X, 5.0, 5.1
Date: December 30, 2014
Filter Group Basics
Filter Groups can simply be thought of as empty “named” objects, or containers, that are used to hold runtime ﬁlter values. These values are broadcast, or published, into the container at runtime with an Outgoing Action, and conversely read from, or listened to, using an Incoming Action.
Filter Group Types
There are two sets of settings that pertain to Filter Groups: “Global” vs. “Current Project”, and “Local” vs. “non-Local”. These two sets of settings are completely independent of each other. This can be confusing since “Global” may naturally appear to pair with “Local”, but this is not the case. The Local/non-Local setting can be applied to both “Global” and “Current Project” Filter Groups.
“Global” vs. “Current Project” accessibility/visibility
- “Global” Filter Groups are accessible (visible) in any Project for a single given Insight instance. “Global” Filter Groups are created in the Admin tool.
- “Current Project” Filter Groups are only accessible (visible) within that same given Project in which they are created.
Note: Identically named “Current Project” Filter Groups will behave the same as a “Global” Filter Group (they must also have matching local/non-local setffng) and will function across Projects when more than one Project is used in a single dashboard.
“Local” vs. “non-Local” broadcast scope
- “Local” broadcast is for the current view and any children only – it does not broadcast upwards to any parents or sideways to any peers (an example of a peer would be two view holders located in a single parent view).
- “Non-Local” broadcast is for entire Project, and aﬀects any children, parents, and peers being shown in a given dashboard view.
Keywords: Altosoft, Insight, filter, groups, driver, drivergroups