> 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-operator-for-sub-organizations.md).

# 子组织的文档操作符

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3aa1a4251e28a79223445b4b00f5077e9725ff37%2Fimage%20(96).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/document-operator-for-sub-organizations.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.
