> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/validation-workflow-rules.md).

# Validation / Workflow Rules

### Validation Rules: Overview <a href="#validation-rules-overview" id="validation-rules-overview"></a>

Validation rules ensure that data entered into a Salesforce record meets specific criteria before saving. These rules are composed of a formula or expression that evaluates one or more fields and returns **True** (invalid) or **False** (valid). When a rule returns True, a specified error message is shown to the user.

***

#### Disable Validation Rules <a href="#disable-validation-rules" id="disable-validation-rules"></a>

When the **Disable validation rules** checkbox is selected during a DataLoader job, all validation rules associated with the relevant Salesforce objects are temporarily deactivated. Data is then migrated to the destination sandbox. Once migration is complete, the validation rules are reactivated automatically.

<figure><img src="/files/VNqDQWvJPBJyI3u1hSt4" alt="Checkbox UI to disable validation rules in Data Loader"><figcaption></figcaption></figure>

Starting with ARM version 20.1, all validation rules are listed in the ARM UI. Users may review and manually re-enable rules as needed.

<figure><img src="/files/D8xb0kH1vj4DiGdZWf8A" alt="List of validation rules in ARM interface"><figcaption></figcaption></figure>

**Screen 1: Successful Validation Rule Execution**

<figure><img src="/files/yMw17PoTVVU5pKXd9Ofc" alt="Validation rules that executed successfully"><figcaption></figcaption></figure>

**Screen 2: Failed Validation Rule Execution**

<figure><img src="/files/ntm3Rc8R4GIyRvjbbPRa" alt="Validation rules that failed execution"><figcaption></figcaption></figure>

***

### Workflow Rules: Overview <a href="#workflow-rules-overview" id="workflow-rules-overview"></a>

Workflow rules automate standard processes and procedures. They typically follow an **if/then** logic model—triggering actions when specified conditions are met.

***

#### Disable Workflow Rules <a href="#disable-workflow-rules" id="disable-workflow-rules"></a>

Selecting the **Disable workflow rules** checkbox during the DataLoader job will deactivate all applicable Salesforce workflow rules during data migration. After the migration is complete, ARM reactivates the workflows.

<figure><img src="/files/gG7vArN9XymCHj0bUMtU" alt="UI showing workflow rules disable checkbox"><figcaption></figcaption></figure>

Similar to validation rules, ARM also displays all workflow rules, allowing users to re-enable them if needed.

<figure><img src="/files/E71o23n2cCxONSGXkTeh" alt="List of workflow rules in ARM UI"><figcaption></figcaption></figure>

**Screen 1: Successful Workflow Rule Execution**

<figure><img src="/files/J2NcxUf4VsJ4FTzJDDO5" alt="Successfully executed workflow rules"><figcaption></figcaption></figure>

**Screen 2: Failed Workflow Rule Execution**

<figure><img src="/files/uQAsBlVN8RFfbFrMjzID" alt="Workflow rules that failed execution"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/validation-workflow-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
