# Rules

Rule steps allow you to run alternative or simultaneous sequences based on specific conditions.

There are three types of rule steps:

* **Conditions** - allows you to set up a conditional logic that will create and (later) run different workflow branches based on whether a condition (or conditions for the "Switch") is met
* **Parallelize** - allows running multiple branches in parallel, simultaneously
* **Delay** - can specify the delay (in seconds) between the steps

![](/files/L7fblfxJavc3o2CvaCn9)

### Conditions

#### **Yes/No condition** 

It creates two branches in the workflow tree and one condition which, if met, will run the "Yes" branch and if not met, will run the "No" branch.

In the majority of cases, to create a simple **IF rule**, you'll use the **EQ()** formula **(1)**. It has two values (arguments), that can be static or could be referenced dynamically from other components **(2)** or pretty much anywhere in the app.

{% hint style="info" %}
If using **text** (string) for a condition, put it into the quotes "\_"
{% endhint %}

![](/files/vRWhTerBLDXnTW9S6ET7)

#### **Switch condition** 

It allows to creation of multiple branches and sets an individual rule for each branch. Only when an individual condition is met will the corresponding branch run, or you can set an *ELSE* condition to run when other conditions are not met.

![](/files/nwOcIOs5l0el0IDcdXA4)

### Parallelize

This rule step allows the creation of multiple branches, all of which will **run simultaneously** (in parallel). It's effectively the same as the "Switch" rule, where each condition is set to "1" (true)

![](/files/IJYkEPAiIdhaYn0bNqbb)

### Delay

With the **delay step**, you can insert a time lag between steps so that the next step will "wait" N seconds after the previous step is fired

![](/files/Cea4s2RlujTgLKb92aZc)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jetadmin.io/user-guide/workflow/steps/rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.