> 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/logic/decision-table-has-returns.md).

# 决策表有返回值

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

## **用途：**

此 DocBits 卡片用于检查指定的决策表是否针对给定文档返回值，并确定是否应在后续工作流步骤中使用返回的数据。它可确保工作流能够根据决策表的结果动态调整。

## **功能：**

* \*\*决策表验证：\*\*此卡片会验证所选决策表是否为正在处理的文档提供返回值。
* \*\*选择决策表：\*\*用户指定要检查的决策表名称。
* \*\*使用返回数据：\*\*用户可以通过 **Boolean** 设置，指定是否在后续卡片中使用返回数据：
  * \*\*True：\*\*返回数据可用，并将在后续工作流步骤中使用。
  * \*\*False：\*\*不使用返回数据，工作流将不依赖该数据继续运行。

## **用法：**

此卡片适用于涉及条件逻辑或基于决策表中预定义规则进行决策的工作流。它可确保决策表输出与工作流流程无缝集成。

## **示例场景：**

* 用户配置此卡片，以检查 **“Invoice Processing Rules”** 决策表是否有返回值。**Boolean** 设置为 **True**，表示返回数据（例如审批要求）将在后续卡片中用于指导工作流决策。

使用“Decision Table Check”卡片，组织可以提高工作流的灵活性，简化基于规则的处理，并确保自动化工作流中的决策保持一致。


---

# 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/logic/decision-table-has-returns.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.
