> 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/document-type-one-of.md).

# 文档类型之一

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

## **用途：**

这张 DocBits 卡片通过验证文档是否符合指定的任一文档类型，确保文档分类正确。当文档可能属于多个类别时，这张卡片尤其有用，可支持更广泛的验证和自动化处理。

## **功能：**

* \*\*多种文档类型验证：\*\*这张卡片允许用户检查文档是否符合一组指定文档类型中的任意一种，从而灵活地对更复杂的文档工作流进行分类。
* \*\*运算符：\*\*用户可以定义条件，根据多种类型验证文档。可用运算符包括：
  * \*\*是：\*\*确认文档符合指定文档类型之一。
  * \*\*不是：\*\*确保文档不符合所选的任何文档类型。
* \*\*文档类型：\*\*用户可以从多种受支持的文档类型中进行选择，包括：
  * \*\*发票：\*\*提交用于付款的财务记录。
  * \*\*借项通知单：\*\*表示应付金额增加的文档。
  * \*\*贷项通知单：\*\*表示应付金额减少的文档。
  * \*\*采购订单：\*\*详细说明买方订单的文档。
  * \*\*订单确认：\*\*确认订单已被接受的文档。
  * \*\*发货通知：\*\*通知即将发货的文档。

## **用法：**

这张卡片适用于需要确保文档被归入多种类型之一的文档管理人员和管理员。它对于文档可能被归入多个类别的工作流尤其有用，可提高自动化程度和分类准确性。

## **示例场景：**

* 用户上传了一份可能是“发票”或“借项通知单”的文档。使用“是”运算符后，这张卡片会确认文档符合所选类型之一，从而让系统应用适当的规则并进行分类。

通过使用“多种文档类型验证”卡片，组织可以提高工作流的灵活性、实现分类自动化，并确保即使适用多种类型，文档也能得到妥善处理。


---

# 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/document-type-one-of.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.