> 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/standard-workflow-builder/workflow-description-conditional-export-trigger.md).

# 工作流示例：条件导出触发器

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

此工作流概述了启动导出流程的条件。它确保只有符合所有指定条件的文档才会进入导出处理，从而提升数据完整性，并确保符合业务规则。

### 何时：

* 系统评估某个文档是否符合导出条件时。

### 逻辑：

1. **文档类型检查**
   * 文档必须属于特定类型（例如“发票”或“收据”）。请指定符合导出流程条件的文档类型。
2. **状态验证**
   * 文档当前状态必须符合预定义条件（例如“已批准”或“可导出”），以表明文档已准备好进行后续处理。
3. **上下文条件**
   * 执行其他检查，以确保文档详情符合特定要求。这些检查可能包括验证订单确认单或采购订单中的信息。请指定必须满足的具体条件。例如：
     * 订单确认单中列出的所有项目均与采购订单中的项目一致。
     * 订单确认单中的总金额与采购订单中的总金额一致。
     * 订单确认单中指定的交货日期与采购订单中的交货日期一致。

### 然后：

#### 操作：

* **启动导出**
  * 如果满足上述所有条件，系统将自动启动该文档的导出流程。
  * 这可能包括生成导出文件、向外部系统发送数据，或在其他应用程序中触发工作流。

#### 实施示例：

```yaml
rules:
  - description: "Conditional Export Trigger"
    conditions:
      - type: "DocumentType"
        criteria: "<SpecifyDocumentType>"
      - type: "Status"
        criteria: "<SpecifyStatus>"
      - type: "DetailMatch"
        criteria:
          - "ItemMatch"
          - "AmountMatch"
          - "DateMatch"
    actions:
      - operation: "StartExport"
```


---

# 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/standard-workflow-builder/workflow-description-conditional-export-trigger.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.