• 1. Context
• 2. Current behavior
• 3. New behavior
• 4. Objective of this change
• 5. Potential impact
• 6. Recommended actions

1. Context

As part of the continuous improvement of the platform, we are evolving the behavior of the following filters:

• “is not”
• “does not contain”

This change applies across all environments:

• Administration platform
• Mobile application
• Studio (automatic selections, manual selections, display conditions, etc.)

2. Current behavior

Today, when using the following filters:

• “is not”
• “does not contain”

👉 Empty fields are excluded from the results

This means that if a value is not filled in, it is not taken into account in the filtering.

3. New behavior

With the upcoming update:

👉 Empty fields will be included in the results

Concretely, a non-filled value will be considered as matching the filters:

• “is not”
• “does not contain”

4. Objective of this change

This update aims to:

• Standardize filter behavior,
• Improve functional clarity,
• Make results more intuitive.

5. Potential impact

This change may impact your usage if you rely on these filters in:

• Your custom views,
• Your searches,
• Your Studio configurations:
• Automatic selections
• Manual selections
• Display conditions

As a result, your filters may return more results than before.

6. Recommended actions

We recommend that you:

• Audit your existing configurations
• Identify where “is not” / “does not contain” filters are used
• Anticipate any necessary adjustments