> 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/document/approve-the-document.md).
# 批准文档
## **用途：**
**“Approve the Document”** 工作流卡片用于将文档标记为已批准。它允许文档进入工作流的下一阶段，从而执行自动化处理或审批工作流。此卡片有助于简化文档管理流程，确保只有已批准的文档才能继续进行后续操作。
## **卡片组件：**
1. **审批状态**
* **描述**：此组件用于将文档标记为已批准。
* **详情**：触发此卡片时，文档的审批状态会更新为已批准。此操作可根据 **“Where”** 和 **“And Sections”** 中定义的条件执行。
## **功能：**
* **条件评估**：系统会评估 **“Where”** 和 **“And Sections”** 中设置的条件。
* 如果**两个条件都为真**，文档将标记为已批准。
* 如果**任一条件为假**，则不会执行此卡片，文档的审批状态保持不变。
* **执行操作**：满足条件后，文档将获批。此更改会反映在文档状态中，使其能够继续沿工作流流转。
## **结论：**
**“Approve the Document”** 工作流卡片是业务工作流中实现文档审批自动化的重要组成部分。通过确保只有符合特定条件的文档才能获批，它有助于保持一致性、减少人工监督，并让文档处理更加顺畅。
---
# 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/document/approve-the-document.md?ask=&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.
.png?alt=media)