> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/developers/paramml-developer-guide/logical-statements-and-test/iif-functions.md).
# "iif" Functions
**List of Logical Statements**
The following are logical statements that can be used within the expressions of **iif** parameters:
**.EQ.** → Equal to (==)
**.NE.** → Not equal to (!=)
**.LT.** → Less than (<)
**.LE.** → Less than or equal to (<=)
**.GT.** → Greater than (>)
**.GE.** → Greater than or equal to (>=)
**.AND.** → AND (&&)
**.OR.** → OR (||)
**.NOT.** → NOT (!)
**Example:**
```xml
```
 In the example provided, if the value of "a" is greater than "b", then the result of "Test1" will be "c". If not, the result will be "d".
In "Test2", a nested "iif" function is utilized to handle more complex tests. If the value of "a" is equal to 1, the result will be "b". If "a" is equal to 2, the result will be "c". If "a" is equal to 3, the result will be "d". And, if "a" is equal to 4, the result will be "e". To view this example in the library, see ()
**Example:**
```xml
```
The dynamic effect coefficient is determined using a formula. If the calculated value is greater than or equal to 1.3, it is set to 1.3. If it is less, the calculated value is used. This is presented as follows: 
```xml
```
.AND. In this expression, both the conditions on the left and right must be satisfied in order for the positive value to be accepted.
The value at which C1 will occur will be 9, as the condition A\C is provided. However, if both conditions are not met simultaneously, C1 will be assigned a negative value. In this case, C1=9. 
```xml
```
.OR. A positive value is accepted if one of the two conditions is met in the statement.
The value at which C1 will occur will be 12 because A\C is provided. If only one of these two conditions is true, the result leads to a positive value. C1 takes the positive value and becomes C1=C. So C=12. 
```xml
```
.EQ. The NULL expression searches for the absence of an object.
C1=E. So C1=50 .  To view this example in the library, see ()
---
# 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.openbrim.org/developers/paramml-developer-guide/logical-statements-and-test/iif-functions.md?ask=&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.