Using Quick Filters

The Quick Filters panel allows you to seamlessly and efficiently narrow down your search results in real time.

Using Quick Filters

Related Video:

Quick Filters have the following sections:

Located in the Left panel are facet filters that allow you to quickly filter through your dataset. We understand how busy our users are and the need for them to quickly filter through the dataset so they can be as productive as possible. We have added ways to better assist your search experience by introducing Recommended attributes. Recommended attributes are suggested attributes based on your search behavior and patterns. It is driven by machine learning techniques such as Classification, Clustering and Collaborative filtering to provide the most likely usable attributes for the specific user. In addition, we have included visual graphical representation of your dataset in attribute facets to guide you in your search experience and get accurate results.

At the top of the Quick Filters panel, you will find the Tenants panel followed by a list of Entity types in the tenant and the aggregated total records. The Tenants panel lists the Customer tenant with all the Data tenants. You can click the Import icon to import the profiles from a data tenant to the customer tenant as shown below. The imported profiles have new Profile IDs in the customer tenant.

Tip: When the import is successful, a check mark is displayed temporarily. After a profile is imported, the Import icon does not appear for that profile.

The data tenants are displayed depending upon your permissions. If you have read-only permissions, you can view the data tenants but you will not be able to import any details because the Import icon will not be available. If you do not have any DTSS permissions, the Search page does not display the Tenants section.

Below the Entity types list, you will find a list of attributes you can filter on. We have laid out this left panel to match your searching behavior. We understand that you will first select the entity type that you want to filter on, then filter down values at the attribute level.

In the attribute section, you will find a list of recommended attributes that dynamically change based on your personal search behavior. Our recommendation engine continues to learn and refines itself based on your history of search events. This allows you to have a quick access to frequently filtered attributes without having to search for them. If you don't find the attributes that you want to filter on, you can search for them using the search bar. The menu includes all the attributes that are marked as 'faceted' in the data model. It first lists Recommended attributes, followed by entity-type specific attributes and finally, Basic attributes. Basic attributes are attributes that are common across all entities like creation date.

When you add attributes, it displays them in the left panel where you can filter on specific values. The attribute facets render based on the data types that you have defined in your data model. As you filter on your dataset, notice that the search result refreshes in real time so you can immediately validate your search query based on the number of search results and records returned.

Adding Default Faceted Attributes

For an entity type, you can make some attributes visible as facets, by default, in the Quick Filters panel. The attributes added as default facets appear in the Quick Filters panel when you select the respective entity type. To enable faceted attributes by default, you must add the required attributes in the defaultFacetedAttributes property as metadata as part of your L3 configuration. To understand about the metadata properties of an entity type and to see an example of the defaultFacetedAttributes property, see The Entity Type topic. You can also see the Attributes Configuration topic that explains the purpose of setting the defaultFacetedAttributes property.

For details on updating your L3 configuration, see Configuration API.
Tip: It is accepted and advisable to perform a GET with Inheritance to understand the consolidated configuration of all the layers (L1, L2, L3). But, when editing the configuration, it is extremely important to Get and Set only the L3 layer of the configuration. To do this you must make another GET request using the _noinheritance option. This retrieves only the L3 layer which is the layer tightly bound to your tenant. Once you have modified it as required, then you must use the Set Configuration API to apply only that L3 layer back to your tenant. Never apply a consolidated configuration to the tenant.