> 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/document-type-operation-one-of.md).
# 文档类型“或”操作
## **用途：**
此卡片用于根据文档类型管理文档操作，通过简单的条件逻辑（是/不是）触发或阻止特定工作流。这有助于精确控制 ERP 系统中不同类型文档的处理方式。
## **卡片组件：**
1. **运算符**
* **说明**：确定应用于文档类型的条件逻辑。
* **选项**：
* **是**：如果文档类型与列表中指定的任一类型匹配，则触发该操作。
* **不是**：如果文档类型与列表中列出的所有类型都不匹配，则触发该操作。
2. **文档类型列表**
* **说明**：指定条件适用的文档类型列表。
* **详情**：列表包含多种文档类型，例如“Invoice”（发票）、“Purchase Order”（采购订单）等；系统将根据这些类型评估条件（是/不是）。
## 功能：
* \*\*条件评估：\*\*系统会根据指定的文档类型列表和运算符条件（是或不是）检查文档类型是否匹配。
* **执行操作：**
* **条件为真：**\
如果文档类型满足指定条件（即属于或不属于该列表），工作流将继续。这可能会触发文档审批、特定验证或路由操作等流程。
* **条件为假：**\
如果文档类型不满足该条件，则执行其他操作，例如拒绝文档或停止工作流。
## 设置和配置：
* 用户通过选择文档类型字段并定义运算符（是或不是）来配置此卡片，然后指定要检查的文档类型列表。配置过程很简单，包括用于选择字段和运算符的下拉菜单，以及用于输入文档类型列表的字段。
## 结论：
“文档类型条件”工作流卡片在精确、灵活地管理基于文档的操作方面发挥着关键作用。借助简单的条件逻辑，它有助于确保妥善处理文档，从而提高效率并确保合规性。清楚地说明此卡片，将帮助用户了解如何有效实施和使用它，使其成为 ERP 系统文档中的重要组成部分。
---
# 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/document-type-operation-one-of.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.
