> 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/chinese/guan-li-yu-she-zhi/workflow/cards-overview/and/document-field/field-is.md).

# 字段是否存在

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-a2adbeed77835a21f19e16a47a4b93e368f4e204%2Fimage%20(50).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## **用途：**

此工作流卡片旨在根据文档中指定字段的存在情况或状态自动执行操作。通过判断该字段为空、缺失还是已填充，它可以帮助工作流精确、准确地处理文档。

## **卡片组件：**

1. **字段名称**
   * \*\*描述：\*\*指定要评估的字段名称。
   * \*\*详情：\*\*该名称必须与文档中使用的确切标识符一致，以确保准确检测字段。
2. **运算符**
   * **描述**：定义根据字段的存在情况或状态触发工作流的条件。
   * **选项**：
     * \*\*为空/不在文档中：\*\*如果字段缺失，或字段存在但为空，则触发工作流。
     * \*\*在文档中/不为空：\*\*如果字段存在于文档中且包含值，则触发工作流。

## **功能：**

* \*\*状态检测：\*\*卡片会监控指定字段，以评估其是否存在及其状态。
* **条件评估：**
  * 系统会根据所选运算符，评估指定字段是否处于定义的状态（为空/不在文档中或在文档中/不为空）。
*

```
**操作执行：**
```

```
* **字段为空/文档中不存在条件：** 如果字段状态符合此条件（即字段在文档中不存在，或存在但为空），系统会启动相关操作。这些操作可能包括生成提醒、标记文档以供审核，或暂停工作流。
* **字段存在于文档中/非空条件：** 如果字段状态符合此条件（即字段存在于文档中且包含一个值），系统会触发相关操作。这些操作可能包括启用后续工作流步骤、更新记录或触发通知。
```

## **设置和配置：**

* 用户可从可用文档字段列表中选择字段，并通过下拉菜单选择运算符。菜单提供“为空/不在文档中”或“在文档中/不为空”选项，含义清晰明确。

## **结论：**

“字段存在与状态验证”工作流卡片是文档处理工作流中的重要工具，可确保准确处理缺失或已填充的字段。通过根据字段状态自动执行操作，该卡片有助于提高数据完整性、减少错误，并确保工作流顺畅、高效地运行。


---

# 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/chinese/guan-li-yu-she-zhi/workflow/cards-overview/and/document-field/field-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.
