> 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/table/item-receiving-method.md).

# 项目接收方式

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

## **用途：**

此 DocBits 卡片用于检查数据集中的项目是否采用指定的接收方式。用户可以根据所选条件验证数据集中的**任意**项目或**所有**项目，因此适用于工作流依赖项目接收方式的场景，例如供应链管理或库存跟踪。

## **功能：**

* **接收方式验证：此卡片会根据指定条件验证项目的接收方式。用户可以选择数据集中的任意**项目或**所有**项目，并将条件设为**等于**或**不等于**。
* \*\*项目选择：\*\*用户可以指定：
  * \*\*任意项目：\*\*只要至少有一个项目符合指定的接收方式条件，卡片就会触发。
  * \*\*所有项目：\*\*只有所有项目都符合指定的接收方式条件时，卡片才会触发。
* \*\*运算符：\*\*可以使用以下运算符定义条件：
  * \*\*等于 (=)：\*\*检查接收方式是否与指定值匹配。
  * \*\*不等于 (≠)：\*\*确保接收方式与指定值不匹配。

## **用法：**

此卡片适用于仓库经理、库存协调员或物流人员，他们需要在执行后续操作（例如处理、存储或发货）之前验证项目的接收方式。

## **示例场景：**

* 用户将卡片配置为检查**所有项目**的接收方式是否**等于“直接交付”**。如果每个项目都符合此条件，工作流就会继续，从而确认所有项目均计划直接交付。

使用“接收方式验证”卡片，组织可以确保符合接收协议、改进物流工作流，并根据具体接收方式保持项目处理的准确性。


---

# 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/table/item-receiving-method.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.
