> 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/status/change-status-to.md).
# 将状态更改为
## **用途：**
\*\*“更改状态”\*\*工作流卡用于将文档状态更改为预定义状态之一——**错误、已拒绝、待验证、待审批、待二次审批**，并可根据状态更改触发相关工作流。此卡可自动完成状态更新和工作流触发，帮助高效管理文档并处理错误。
## **卡片组件：**
1. **状态**
* **说明**：指定要应用于文档的新状态。
* **选项**：
* **错误**：标记文档发生错误。
* **已拒绝**：表示文档已被拒绝，不会继续处理。
* **待验证**：将文档设为待处理状态，由下一位用户或系统流程审核并验证。
* **待审批**：将文档置于待审批状态。
* **待二次审批**：如果适用，将文档暂缓处理，等待第二级审批。
2. **触发工作流**
* **说明**：确定状态更改后是否应触发后续工作流。
* **选项**：
* **True**：根据状态更改启动相关工作流。
* **False**：状态更改后不执行工作流。
## **功能：**
* **条件评估**：系统评估 **“Where”** 和 **“And Sections”** 中设置的条件。如果这些条件为真，卡片会将文档状态更改为所选值。
* **状态更新**：满足条件后，系统会根据用户的选择，将文档状态更新为预定义选项之一（错误、已拒绝、待验证、待审批、待二次审批）。
* **触发工作流操作**：如果 **触发工作流** 设置为 **True**，系统会在状态更新后自动启动相关工作流。如果设置为 **False**，则不会触发其他工作流，流程在状态更改后结束。
## **设置与配置：**
配置此卡片时，用户需要：
1. 指定条件评估后要为文档设置的 **状态**（错误、已拒绝、待验证、待审批或待二次审批）。
2. 选择状态更改后是否 **触发工作流**，并设置为 **True** 或 **False**。
3. 仅当 **“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/status/change-status-to.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)