> 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/settings/document-processing/module/workflow-builder.md).

# 工作流构建器

### 概述

**Workflow Builder** 设置会为您的组织启用 **DocFlow**。DocFlow 是工作流引擎，用于自动处理文档的流转、审批步骤、条件和后续操作。启用此设置后，DocFlow 工作流设计器将变为可用，文档也会开始按照您创建的工作流流转。

此功能**基于订阅**，默认**处于禁用状态**。

### 它有什么作用？

开启此开关并非只是切换一个开关，而是会启动 **DocFlow 订阅**。系统会显示一个对话框，供您选择 DocFlow 计划（DocFlow Standard，以及可选的 DocFlow Advanced）。确认订阅后，此设置才会启用。

* **已启用** — DocFlow 已为组织激活。文档会通过您的工作流流转，并且可以使用 Workflow Builder 设计器创建和编辑工作流。
* **已禁用** — DocFlow 已关闭，相关订阅也会取消。文档不再通过工作流处理。

{% hint style="info" %}
**Workflow Builder 是用于为整个组织开启或关闭 DocFlow 的主开关。** 由于它管理订阅，启用时会打开计划选择对话框，禁用时会取消当前 DocFlow 订阅。
{% endhint %}

### 优势

* **自动化**：用自动化步骤（流转、审批、条件）替代人工交接。
* **一致性**：每份文档都遵循相同的既定流程。
* **可见性**：在同一位置设计和管理工作流。

### 如何使用

1. 前往 **Settings**。
2. 选择 **Document Processing**。
3. 选择 **Module**。
4. 打开 **Document Type** 部分。
5. 找到 **Workflow Builder**，然后开启开关。
6. 在对话框中选择 DocFlow 计划（Standard，可选 Advanced），并确认。创建订阅后，DocFlow 即会启用。
7. 然后，在 DocFlow 中设计文档工作流 — 有关如何构建工作流，请参阅[工作流](/chinese/guan-li-yu-she-zhi/workflow.md)部分。

### 何时使用此功能

* **自动化文档流程**：当文档需要按照既定步骤流转时，例如审核、审批或路由。
* **团队工作流**：当处理文档需要多个员工或角色参与时。
* **保持关闭**：如果您的组织不使用 DocFlow / 文档工作流（关闭此功能也会取消 DocFlow 订阅）。


---

# 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/settings/document-processing/module/workflow-builder.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.