> 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/then/assignee/assign-document-to-matching-sub-organization.md).

# 将文档分配给匹配的子组织

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

## **用途：**

\*\*“根据字段将文档分配给匹配的子组织”\*\*工作流卡片会根据文档中的指定字段，动态地将文档分配给子组织。如果未找到匹配的子组织，卡片会使用预先设定的备用子组织。

## **卡片组件：**

1. **字段名称**
   * \*\*说明：\*\*指定用于确定匹配子组织的文档字段。
   * \*\*详情：\*\*卡片会查找指定字段中的值，并将其与可用子组织进行匹配。
2. **子组织（备用）**
   * \*\*说明：\*\*定义在指定字段中未找到匹配项时使用的备用子组织。
   * \*\*详情：\*\*如果字段值与任何子组织都不匹配，文档将被分配给所选的备用子组织。

## **功能：**

* **条件评估：**\
  只有当 **“Where”** 和 **“And Sections”** 的评估结果均为 true 时，卡片才会执行操作。
* **动态分配：**\
  卡片会检查指定字段的值，并将文档分配给与该值匹配的子组织。
* **备用机制：**\
  如果未找到匹配的子组织，文档将被分配给备用子组织。

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

* **选择字段名称：**\
  选择文档中包含待匹配子组织值的字段。
* **选择备用子组织：**\
  选择在文档字段中未找到匹配项时使用的子组织。

## **结论：**

\*\*“根据字段将文档分配给匹配的子组织”\*\*工作流卡片可以灵活地将文档动态路由到相应的子组织，并提供备用选项，确保每份文档都能分配到子组织。


---

# 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/then/assignee/assign-document-to-matching-sub-organization.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.
