> 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/and/status/document-status-condition-list.md).
# 文档状态条件列表
**用途**
此卡片用于根据文档的当前状态，通过条件逻辑控制工作流操作，从而触发或限制特定流程。它可确保文档只有在满足预定义的状态条件时，才会继续通过工作流。
**卡片组件**
1. **运算符**
* **说明**：确定如何根据指定条件评估文档状态。
* **选项**：
* **是**：如果文档的当前状态与指定状态之一匹配，则触发相关操作。
* **不是**：如果文档状态与指定状态均不匹配，则触发相关操作。
2. **状态（列表）**
* **说明**：列出用于与文档当前状态进行比较的特定状态。
* **示例**："Error"（错误）、"Export Error"（导出错误）、"Ready in Validation"（已准备好验证）、"Ready in Review"（已准备好审核）、"Pending Approval"（待审批）、"Pending Second Approval"（待二次审批）。这些状态代表文档在工作流流程中可能处于的不同阶段或状态。
**功能**
* **状态识别**：文档在 ERP 系统的工作流中流转时，自动识别其当前状态。
* **条件评估**：将所选运算符（是或不是）应用于文档状态，并与列出的状态进行比较：
* 如果选择**是**，则检查文档状态是否与列表中的任一状态匹配。
* 如果选择**不是**，则检查文档状态是否未出现在列表中。
* **执行操作**：根据条件评估结果：
* **为真**：如果满足条件，则执行预定义的操作或工作流。
* **为假**：如果不满足条件，则跳过或触发其他工作流。
* **工作流集成**：与其他工作流组件无缝集成，确保文档处理在整个系统中协调进行。
**用户交互**
* **设置和配置**：用户通过选择运算符并指定相关状态来配置此卡片。配置时可能需要使用简单的下拉菜单或复选框来选择状态和运算符。
* **监控和管理**：用户可以通过仪表板跟踪卡片的活动，查看正在监控的状态条件，以及根据这些条件采取的操作。
* **错误处理和提醒**：支持设置流程失败或文档状态与预期不符时的提醒，以便快速响应运营问题。
#### 结论
“文档状态条件”工作流卡片对于确保文档根据其当前状态得到正确处理至关重要，有助于加强 ERP 系统中的控制并提升效率。在系统手册中清晰地说明此卡片，将帮助用户有效地实施和管理它，并利用其功能维护顺畅且合规的文档工作流。此卡片在管理文档生命周期、确保只有满足特定条件的文档才能进入业务流程后续阶段方面尤其有用。
---
# 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/and/status/document-status-condition-list.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.
