> 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/export/export-with-export-configuration.md).

# 使用导出配置导出

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

## **用途：**

\*\*“使用导出配置导出文档”\*\*工作流卡片用于使用指定的导出配置导出文档。它支持忽略与文档关联的待处理任务，确保无论文档当前处于什么状态，都能顺利完成导出。

## **卡片组件：**

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/export/export-with-export-configuration.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.
