Difference between revisions of "HowTo:Configure Hierarchy Filtering"
(→Client) |
(→Client) |
||
| Line 14: | Line 14: | ||
* list of settings (one per property) | * list of settings (one per property) | ||
* each setting contains: | * each setting contains: | ||
| − | ** | + | ** property name |
| − | ** | + | ** property level |
| − | ** | + | ** default matching mode |
<source lang="xml"> | <source lang="xml"> | ||
<?xml version="1.0" encoding="utf-8"?> | <?xml version="1.0" encoding="utf-8"?> | ||
Revision as of 12:38, 21 November 2017
Hierarchy Filtering allows the UBIK data designer to provide filter rules for the global object hierarchy on the client. For example, if a user wants to see all objects having the color green and a certain progress value, we have to create hierarchy filter rules - only allowing to view filterable objects that meet both of these criteria. When the filter is applied, objects that do not meet the criteria will be invisible. This means they will not be seen when browsing through the data and not even be found when doing queries or search operations. The designer can decide which objects are affected by the filtering by declaring objects as hierarchy filterable objects. These will be filtered based on the defined criteria. In addition, the designer can also declare objects to be hierachy filterable folder objects. These objects are filtered depending if there is visible content inside the data branch beneath this object. By defining these objects and rules, it is possible to thin out whole data branches depending on filter rules.
