> 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/reject-the-document.md).

# 拒绝文档

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

## **用途：**

\*\*“拒绝文档”\*\*工作流卡片用于在工作流中将文档标记为已拒绝。此操作会停止文档的处理进度，并阻止其进入工作流的下一阶段。它可以确保不符合必要条件或标准的文档被标记，并停止进一步处理。

## **卡片组件：**

1. **拒绝状态**
   * **描述**：此组件会将文档标记为已拒绝，表示该文档未满足审批所需条件。
   * **详情**：触发此卡片时，文档状态会更新为“已拒绝”。此决定基于 **“Where”** 和 **“And Sections”** 中设置的条件。

## **功能：**

* **条件评估**：系统会评估 **“Where”** 和 **“And Sections”** 中设置的条件。
  * 如果**两个条件都为真**，文档将被拒绝。
  * 如果**任一条件为假**，卡片将不会执行，文档状态保持不变。
* **执行操作**：满足条件后，文档会被标记为已拒绝。此操作可确保只有符合特定标准的文档才能继续处理，其他文档则会被标记并停止处理，以供审核或更正。

## **结论：**

\*\*“拒绝文档”\*\*工作流卡片是控制自动化流程中文档流转的重要工具。通过允许拒绝不合规的文档，它可以确保只有有效且准确的文档继续通过工作流，从而提高文档管理的效率和准确性。


---

# 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/reject-the-document.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.
