> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/operators/or.md).

# Or

Combine boolean conditions so any true input produces a true result.

Use **Or** when any one of several conditions should allow the next action. For example, combine temperature checks for above `25` or below `18`.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-437a6e810dcabfadd7488c353947780da2842ce8%2Frule-chain-or-palette.png?alt=media" alt="Or entry in the Operators palette."><figcaption><p>Or in the palette</p></figcaption></figure>

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-9c7a68d5dde0e86e2a04f8c80e0c593e9692f0b3%2Frule-chain-or-node.png?alt=media" alt="Configured Or node with two boolean inputs and one output."><figcaption><p>Or configured for two conditions</p></figcaption></figure>

## Inputs and outputs

* **Inputs:** Blue boolean conditions.
* **Output:** `true` if at least one input is true. It is `false` only when all inputs are false. Additional output pins carry the same result.

Or combines the input values during an execution. It does not start the chain.

## Configurable settings

Open the node's gear icon to change its settings.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-01afa10ca427cd46f871a002f5ab3f8c940b6519%2Frule-chain-or-settings.png?alt=media" alt="Or settings with two inputs, one output and a note, with callouts A to D."><figcaption><p>Or settings</p></figcaption></figure>

| Reference | Setting     | Purpose                                                             |
| --------- | ----------- | ------------------------------------------------------------------- |
| **\[A]**  | Input pins  | Set `1` to `100` inputs. Use one pin for each condition to combine. |
| **\[B]**  | Output pins | Set `1` to `100` output pins for the same result.                   |
| **\[C]**  | Note        | Explain the combined conditions on the node.                        |
| **\[D]**  | Save        | Apply the node settings. Save the chain separately in the editor.   |

## Combine two temperature checks

Before you begin, [open the rule chain editor](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/open-the-configuration-of-an-existing-rule-chain.md). Configure two [Condition](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/conditions/condition.md) blocks for the same numeric temperature: **GT (Greater than)** `25` and **LT (Less than)** `18`. Keep the chain paused while configuring.

1. Drag **Or** from **Operators** onto the workspace.\
   ▷ The settings window opens.
2. Set **Input pins** **\[A]** to `2`.
3. Set **Output pins** **\[B]** to `1`.
4. Enter `Outside temperature range` in **Note** **\[C]**.
5. Click **Save** **\[D]**.
6. Connect the GT output to the first Or input.
7. Connect the LT output to the second Or input.
8. Connect the Or output to the next block.
9. Set the [execution order](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md#set-order) so both Conditions run before Or and the next block runs after it.
10. Click **Save** in the editor.

When the chain executes, a temperature of `27` or `16` produces `true`. A temperature of `21` produces `false`.

## Related documentation

* [And](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/operators/and.md) when every condition must be true.
* [Not](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/operators/not.md) to invert a boolean result.
* [Configure Rule Chain](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md) for connections and chain triggers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/operators/or.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
