> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/and/document-field/docfield-is.md).

# Docfield is

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-7b87efeeec3d21930f9248e19411818d5208fc2a%2Fimage.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## **Purpose:**

This workflow card is designed to automate actions by comparing a specified document field's value with a reference value or condition. It ensures dynamic and accurate decision-making in workflows based on document data validation.

## **Components of the Card:**

1. **Field Name**
   * **Description:** Specifies the name of the document field to be evaluated.
   * **Detail:** This must match the exact identifier of the field within the document.
2. **Operators**
   * **Description:** Defines the type of comparison to be performed between the field value and the reference value.
   * **Options:**
     * **Equals (=):** Checks if the field value matches the reference value.
     * **Not Equals (≠):** Ensures the field value differs from the reference value.
     * **Greater Than (>):** Confirms the field value is greater than the reference value.
     * **Greater or Equals (≥):** Validates the field value is equal to or greater than the reference value.
     * **Lesser Than (<):** Checks if the field value is less than the reference value.
     * **Less or Equals (≤):** Ensures the field value is less than or equal to the reference value.

## **Functionality:**

* **Condition Evaluation:** The system checks whether the document field's value, in relation to its associated column, satisfies the comparison condition specified by the operator and reference value.
* **Action Execution:**
  * **True Condition:**\
    If the document field's value meets the specified condition (e.g., equals the reference value), the system triggers the associated actions. These could include updating records, progressing the workflow, or generating notifications.
  * **False Condition:**\
    If the document field's value does not meet the specified condition, alternative actions or no actions are executed, based on the workflow configuration.

## **Setup and Configuration:**

* The user selects the field name of the relevant document and chooses the operator from the drop-down menu. The user then specifies the reference field value to complete the configuration.

## **Conclusion:**

The "DocField Comparison Validation" workflow card is a robust tool for dynamic document processing. By automating actions based on field comparisons, this card streamlines workflows, enhances accuracy, and supports data-driven decision-making.

## Practical example

**When to use:** Review invoices above a defined amount.

**Configuration:** Select numeric field `total_amount`, operator `>` and reference value `1000`.

**Expected result and counterexample:** A value of `1200` satisfies the condition. `1000` and `900` do not: the `>` operator requires a value strictly greater than `1000`.

This is an illustrative configuration and expected outcome. Use fields, users and groups configured in your test organization; it is not a claim that this example was executed.


---

# 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.docbits.com/administration-and-setup/workflow/cards-overview/and/document-field/docfield-is.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.