> 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/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/document-flow.md). # 文档流 **文档流**显示单个文档的处理步骤。您可以用它查看哪些步骤已完成、哪个步骤正在等待，以及处理耗时。以下示例使用英文 Sandbox 中的一张合成发票。 ## 从仪表板打开在**仪表板**上找到该文档。在其**操作**列中，选择三个点，然后选择**文档流**。此选项会打开该文档的流程视图；不会更改文档。

英文仪表板中打开了操作菜单，其中显示一张合成发票；“文档流”列在“分配给”下方。 — 从文档的“操作”菜单中选择“文档流”。

## 从字段验证打开打开该文档。在**字段验证**中，选择右侧操作栏中的三个点，然后在**更多选项**下选择**文档流**。

英文“字段验证”界面，显示“更多选项”菜单及其中的“文档流”选项，旁边是一张合成发票。 — 也可以从文档视图打开相同的流程。

## 阅读流程左侧的**流程统计**汇总了步骤总数、已完成和正在等待的步骤数、重新启动次数、总耗时、当前状态和整体进度。每张编号卡片都显示一个处理步骤及其当前状态。向下滚动可查看后续步骤。

英文“文档流”界面，左侧显示“流程统计”，并显示前几张编号步骤卡片：已导入、文档已导入和 OCR。 — 合成发票流程中的前几个步骤。

向下滚动后的英文“文档流”界面；后续卡片包括分类、字段提取、表格提取、转换器、元数据填充器、查找数据和验证器。 — 向下滚动可查看后续步骤的顺序。

选择某张步骤卡片，可在左侧打开**步骤详情**。其中会显示模块及其状态。右侧也可能打开**任务日志**面板；日志详情取决于该任务可用的信息。选择“步骤详情”中的\*\*×\*\*可关闭面板。

英文“文档流”界面中选中了 OCR 卡片；“流程统计”下方的“步骤详情”显示模块为 OCR，状态为已完成。 — “步骤详情”会说明所选模块的状态。

--- # 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/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/document-flow.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.