Manage Filter Rules

Members with the required privileges can use query pipeline filters to easily define the scope of the search results displayed to your users.

Filter rules allow you to enter hidden query expressions to be added to all queries going through the related query pipeline. While this feature permits the addition of any query syntax expression to any part of the query expression (i.e., q, aq, cq, dq, or lq), query pipeline filters are typically used to add a field-based expression to the constant query expression (cq).

Example

A support agent authenticates on a customer service search interface. A query pipeline filter rule adds the expression NOT @source=="Marketing" to ensure that marketing items don’t appear when the end-user is identified as a support agent. The cq is then always NOT @source=="Marketing" when support agents send queries.

The list of filters in a pipeline is empty by default. Filter rules are defined independently for each pipeline.

Create Filter Rules

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline in which you want to add a rule, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left-hand side of the page, select Filters.

  4. In the upper-right corner of the page, click Add Rule to access the Add a Filter Rule [1] subpage.

  5. In the Query Parameter drop-down menu, select the query parameter in which the filter will be included in an AND expression.

  6. In the Content that matches section, depending on the mode, use the drop-down menus or the input to provide the desired filter expressions.

  7. On the right-hand side, under Condition, you can optionally select a query pipeline condition in the drop-down menu or create a new one.

  8. Under Description, optionally enter information that will help you manage the rule in the future.

  9. Click Add Rule.

Edit Filter Rules

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline in which you want to edit a rule, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left-hand side of the page, select Filters.

  4. Click the rule you want to edit, and then click Edit in the Action bar [2] to access the Edit a Filter Rule subpage.

  5. In the Query Parameter drop-down menu, select the query parameter in which the filter will be included in an AND expression.

  6. In the Content that matches section, depending on the mode, use the drop-down menus or the input to update the desired filter expressions.

  7. On the right-hand side, under Condition, you can optionally select a query pipeline condition in the drop-down menu or create a new one.

  8. Under Description, optionally enter information that will help you manage the rule in the future.

  9. Click Save.

Duplicate Filter Rules

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline for which you want to duplicate query pipeline rules, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left-hand side of the page, select Filters.

  4. In the Filters subtab, click the rule you want to duplicate within the same pipeline (typically to create a slightly different rule).

  5. In the Action bar, click Duplicate.

The duplicated rule appears at the bottom of the list in the pipeline component tab.

Review Information About the Rule’s Creation or Last Modification

You can verify who created or last modified a given filter rule by inspecting the Details column of the Filters subtab. The Details column also indicates the hour and date the rule was created or last modified.

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline containing the rule for which you want to inspect the information of the Details column, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left side of the page, select Filters.

  4. In the Filters subtab, inspect the information of the Details column for the desired rule.

Delete Filter Rules

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline for which you want to delete query pipeline rules, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left-hand side of the page, select Filters.

  4. In the Filters subtab, click the rule you want to delete.

  5. Click Delete to confirm.

Change the Rule Order

Query pipeline rules are executed in the order in which they appear on the page until a condition is satisfied.

  1. On the Query Pipelines (platform-eu | platform-au) page, click the query pipeline for which you want to manage the rules' execution order, and then click Edit components in the Action bar.

  2. On the page that opens, select the Advanced tab.

  3. In the Advanced tab, on the left-hand side of the page, select Filters.

  4. In the Filters subtab, click the rule whose position you want to change.

  5. In the Action bar, click Move up or Move down to change the position of the rule.

Leading Practices

Consider the following leading practices when creating filter rules:

Don’t Use Filter Rules to Exclude Sensitive Information

Filters, by themselves, don’t prevent the exposure of filtered content. We therefore strongly advise against creating a source whose content is accessible to everyone and using a pipeline filter to exclude sensitive information.

In the following cases, sensitive content from a source whose content is accessible to everyone could be exposed:

  • A filter rule based on the aq query parameter is set on a query pipeline that contains an ART model for which the Match the advanced query option is disabled.

  • Using other pipelines not having a similar filter from other search interfaces or directly from the API.

  • A colleague not understanding the reason for the filter could modify or remove the filter.

You can ensure security by enforcing the search hub at the search token level (see Search Token Authentication). Moreover, search hubs defined on the client-side that are used as conditions in pipelines do not safeguard the security of the filtered content.

Use Inclusion Filters

When creating filters, specify what the pipeline should include rather than exclude (e.g., @source==(“Source 1”, “Source 2”) rather than NOT @source==(“Source 3”)) to prevent new source content or content types in your organization index from appearing in search results.

If you only use an exclusion filter you must modify the filter expression whenever new content is added to your organization index. To provide a controlled deployment of new sources into search results, use an inclusion filter, which allows content to be included in an additive manner. This means content only appears in search results after the filter is updated, not immediately after indexing.

Example

You have three sources (Source 1, Source 2, Source 3) in your index and you want only Source 1 and Source 2 content to appear in the search results of a specific tab:

  • An exclusion filter (e.g., NOT @source==(“Source 3”)), requires you to modify the filter expression if you retrieve content from the newly created Source 4 (e.g., NOT @source==(“Source 3”, "Source 4")).

  • An inclusion filter (e.g., @source==(“Source 1”, “Source 2”)), requires no further changes even if you index Source 4 content.

Check Your Source Mappings

Filter rules filter out from the search results all items that don’t match the hidden query expression on which the rule is based.

Since you will typically use filter rules to add a field-based expression to the cq, all items that must fall within the scope of the filter rule must be mapped with the matching metadata values in order to be displayed in the search results (see Manage Source Mappings). In other words, items that don’t match the defined query expression won’t appear in the search results.

Therefore, you should be 100% certain that all items that must match the filter expression are consistently mapped with the proper metadata.

If you’re not 100% certain that the mappings are totally accurate, you should consider using query ranking expression rules instead.

Apply Filter Rules Conditionally

Typically, filter rules should only apply when a certain condition is fulfilled.

In general, you should ensure that this is the case by associating such a rule, and/or the pipeline it’s defined in, to a global condition.

Moreover, when basing a filter rule on the value of one or more $context keys, you should use a condition to assert that these keys contain values. Otherwise, you risk injecting invalid expressions in the target part of the query expression (i.e., aq, cq, etc.).

Reference

"Content that matches" Section

When creating a rule, under the Content that matches section, you must define filter expressions to target specific content.

You can define filter expressions using either the "Basic Mode" or "Advanced Mode".

Basic Mode

To define filter expressions using the Basic Mode:

  1. In the Select field drop-down menu, use the Filter box to find and select the field that must be targeted by the filter expression.

  2. In the Select a comparator drop-down menu, select one of the available comparators.

  3. If applicable, in the Select a field value drop-down menu, enter or select the values that must be filtered according to the field selected in step 1.

  4. (Optional) Click Add to add another filter expression to the rule. Note that when adding multiple filter expressions to a rule, new filter expressions are appended to the initial expression using the and logic, meaning that only content matching all filter expressions will be affected by the rule.

Advanced Mode

To define filter expressions using the Advanced Mode, enter a query expression using the Coveo query syntax.

QPL Syntax

Use the following query pipeline language (QPL) syntax to define a statement expressing the filter feature:

filter <queryExpressionPart> <expressions>

<queryExpressionPart>

A string indicating the part of the query expression to which one or more query expressions should be appended. Must be one of:

  • aq: The advanced part

  • cq: The constant part

  • dq: the disjunction part

  • lq: the large part

  • q: the basic part

Notes

<expressions>

A comma-separated list of query expressions (e.g., foo, @bar=="baz"). Each of these query expressions will be appended to the current value of the target <queryExpressionPart> using an implicit AND operator (i.e., a whitespace character).

Important

The result set of the constant part (cq) of the combined query expression is kept in a special cache.

Consequently, you should avoid creating filter statements that add dynamic content to the cq, otherwise you risk filling the cache with useless data, which might have a negative impact on performance.

Order of Execution

The following diagram illustrates the overall order of execution of query pipeline features:

order of pipeline execution

Required Privileges

By default, members of the Administrators and Relevance Managers built-in groups can view and edit elements of the Query Pipelines (platform-eu | platform-au) page.

The following table indicates the required privileges to view or edit filter rules (see Manage Privileges and Privilege Reference).

Action Service - Domain Required access level

View filter rules

Organization - Organization
Search - Query pipelines

View

Edit filter rules using the Basic mode

Organization - Organization
Content - Fields

View

Search - Query pipelines

Edit

Edit filter rules using the Advanced mode

Organization - Organization

View

Search - Query pipelines

Edit


1. (Advanced) You can click Menu, and then select Add rule with code to define the rule using the appropriate QPL syntax.
2. (Advanced) You can click More, and then select Edit code to edit the rule using the appropriate QPL syntax.