> 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/compare-with-purchase-order/in-order-confirmation-purchase-order.md). # 订单确认采购订单当需要根据采购订单检查订单确认时，请在工作流生成器中使用 **Compare with Purchase Order**。将此卡片添加到 **And...** 下方，然后选择订单数据、运算符以及结果的处理方式。以下截图展示了英文界面中的两个可用卡片版本。其字段仍为占位内容；保存前请根据自己的工作流进行设置。 ## 将结果写入字段

工作流生成器中的 Compare with Purchase Order 卡片，包含 Order Data、Operator、Text、Field Name 和 Result of condition 占位内容。 — 版本 2：根据条件结果将文本写入字段。

从订单确认中选择 **Order Data**，并选择用于与采购订单进行比较的 **Operator**。输入要写入的 **Text**，选择 **Field Name**，然后选择触发写入的 **Result of condition**。 ## 比较数据

工作流生成器中的 Compare with Purchase Order 卡片，包含 Any/All、Order Data、Operator 和 Comparison Data 占位内容。 — 版本 4：将选定的订单确认数据与采购订单数据进行比较。

选择 **Any/All**，以决定是否必须有一个或所有选定条件匹配。然后选择用于采购订单比较的 **Order Data**、**Operator** 和 **Comparison Data**。有关周边步骤，请参阅 [工作流](/chinese/guan-li-yu-she-zhi/workflow.md) 和 [Compare with Purchase Order](/chinese/guan-li-yu-she-zhi/workflow/cards-overview/and/compare-with-purchase-order.md)。 --- # 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/compare-with-purchase-order/in-order-confirmation-purchase-order.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.