## Background Static recommendation scope configuration defines fixed filtering rules for recommendation results. Its main value lies in helping businesses quickly exclude items that do not meet basic requirements, such as out\-of\-stock products or blocking specific categories. It suits scenarios with relatively stable business rules, like long\-term blocking of a product category. This article explains the configuration steps and logic of static recommendation scope to help you achieve precise filtering of recommendation results. To meet complex enterprise requirements, this feature supports sophisticated static filtering logic to ensure every recommended item strictly adheres to your business standards. ## Important Information :::warning \*Note 1. The system does not perform mutual exclusion checks. You must ensure the filtering logic is correct during configuration. If mutually exclusive conditions exist, the system will not report errors but will return empty results only. 2. If an item is missing a specific field used in a filter, the system will **automatically ignore** that specific filtering condition for that item. To learn more, please see [Automatic ignore logic](/docs/85296/1791113#545109f8). ::: ## Configuration Steps 1. In the platform's left navigation, select ** Scope** \> **Define Recommendable Items** to open the static recommendation scope configuration page.

### 1. Basic filter configuration (suitable for simple business rules) 1. Select **AND** (all conditions must be met) or **OR** (any condition can be met) from the "Logical Operator" dropdown list. 2. Click "Add Rule" and set up the following items: |**Configuration item** |**Description** | |---|---| |Logical operator |Select condition combination logic (AND requires all conditions to be met, OR requires any one condition to be met). | |Filter field |Select an item field from the dropdown list|\ | |:::tip \*Note|\ | |The filter field supports only fields marked as "Filterable".|\ | ||\ | |:::| |Condition type |Select a matching rule, such as `contains (in)`, `does not contain (not in)`, or numerical range comparison. | |Condition value |Enter matching value. | ### 2. Nested logic configuration (suitable for complex business rules) Supports creating condition groups to achieve compound logic like (A and B) or C, **with up to 1 level of nesting**: |**Configuration item** |**Description** | |---|---| |Outer logical operator |Define the top\-level logical relationship between condition groups (AND/OR). | |Nested condition group |Create independent condition groups and configure internal logic (define rules within the group through internal logical operators). | |Field/condition/value |The configuration method is consistent with *basic filtering* logic, supporting the combination of multiple filter conditions within a condition group. | ### Condition types \- supported data types :::tip \*Description The filtering functions for the **Publish Time** field and the **Timestamp** field are currently in public beta. To try it, contact Volcano Engine to activate it for you. ::: |

|

|

|

|

|

|

|

|

|\ |Condition type

|String

|Integer

|Float

|Array

|Boolean

|Publish time field

|timestamp field

|Object

|\ | | | | | | | | | | |---|---|---|---|---|---|---|---|---| |

|

|

|

|

|

|

|

|

|\ |found in

|✅

|\-

|\-

|✅

|\-

|\-

|\-

|Not supported

|\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |not found in

|✅

|\-

|\-

|✅

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |in range

|\-

|✅

|✅

|\-

|\-

|✅

|✅

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |less than / earlier than

|\-

|✅

|✅

|\-

|\-

|✅

|✅

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |less than or equal to

|\-

|✅

|\-

|\-

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |greater than / later than

|\-

|✅

|✅

|\-

|\-

|✅

|✅

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |greater than or equal to

|\-

|✅

|\-

|\-

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |equals

|\-

|✅

|\-

|\-

|✅

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |not equal to

|\-

|✅

|\-

|\-

|✅

|\-

|\-

| |\ | | | | | | | | | | ### Automatic ignore logic When an item is missing the specific field required by a filtering condition, the system will **automatically ignore** that condition for the affected item. Using **missing field in filter condition A** as an example, the platform’s default handling logic is as follows: |**Filter condition configuration** |**Final output** | |---|---| |A AND B |Item does not meet filter conditions | |A OR B |According to the result of **B filter condition** | |A AND (B AND C) |Item does not meet filter conditions | |A AND (B OR C) |Item does not meet filter conditions | |A OR (B AND C) |According to the result of the **(B AND C) filter criteria** | |A OR (B OR C) |According to the result of the **(B OR C) filter criteria** | |B AND (A OR C) |According to the result of the **(B AND C) filter criteria** | |A AND (A AND C) |Item does not meet filter conditions | |A OR (A AND C) |Item does not meet the filter conditions | --- ## Dynamic filtering In some recommendation scenarios, users may want to filter results based on personal preferences. For such needs, you can use the dynamic filtering feature. The operation process is as follows: 1. Complete the dynamic filtering configuration on the platform. 2. When requesting the recommendation service API, return the configured filter attribute values to achieve dynamic filtering. For details, please refer to: [Configure Dynamic Filter Conditions](/docs/85296/1863360)

Viking AI Search