---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# OR conditions

# OR conditions {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

The condition builder uses two different types of OR conditions: top-level and
dependent.

Using a dependent OR condition, you can specify alternative criteria to a single operation.
Dependent OR conditions work in the manner A and (B or C). When you have an OR condition in
the query, the magnifying glass is no longer available. The conditions you put in the quick
search headers are ANDed together. Having an OR makes it ambiguous as to where the new
condition should go, for example before the OR, or after the OR.

For example, to return a list of all unassigned problem and incident records from the Task
table, create a filter with a dependent OR on the Number field.

\[Assigned to\] \[is\] \[empty\] AND \[Number\] \[begins with\] \[PRB\] OR \[Number\] \[begins with\] \[INC\].  
Figura 1. Dependent OR

A top-level OR condition allows you to display the results of multiple filter criteria in a
single list. Top level OR conditions work in the manner (A and B) or (C and D).  
For example, to return a single list of all active incidents with a category of hardware, and all inactive incidents with a category of software, create two condition sets separated by a top-level OR condition.

* \[Active\] \[is\] \[true\] AND \[Category\] \[is\] \[Hardware\]
* Top level OR condition
* \[Active\] \[is\] \[false\] AND \[Category\] \[is\] \[Software\]
{#c_UsingORConditions__ul_prj_v4k_gp}  
Figura 2. Top level OR

Top-level and dependent OR conditions can be used together. Filters using both types of OR
conditions work in the manner (A or B) or (C or D). By mixing AND conditions with top-level
and dependent OR conditions, you can create very specific filters.
**Tarefas relacionadas**   

* [Create a filter in List](https://servicenow-prod.fluidtopics.net/4aatN~DKvW5_IsAJg~Megg "You can create a filter to restrict what records appear in a list by providing a set of conditions. When you run the filter, only records that meet the specified conditions are listed.")
* [Add related list conditions](https://servicenow-prod.fluidtopics.net/jm2CPvCbWITtgUeFwhEWVQ "Related list conditions allow you to include a relationship with another table in the filter. Related list conditions are supported in both List v3 and the Report interface.")
* [Filter on multiple string values](https://servicenow-prod.fluidtopics.net/k0lLhNzO_nDa5nYXRTe~Aw "For a string field, you can create a filter that searches for multiple values by creating a comma-delimited list.")  
**Referência relacionada**   

* [Dynamic operators](https://servicenow-prod.fluidtopics.net/byaSFVK2nTQPHIAjpeL94A "The dynamic operator, is (dynamic), lists predefined dynamic filter options where the condition value is computed from a value in a reference field.")