> 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/when/page.md).
# 文档类型操作
## **用途：**
此工作流卡片专用于对按类型分类的文档执行预定义操作。它简化了 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/when/page.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.
