> 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/items-have-shelf-life.md).

# 商品具有保质期

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

## **用途：**

此 DocBits 卡片用于验证数据集中的商品是否符合基于保质期设定的条件。用户可以选择验证“任意”商品或“所有”商品，并使用多种比较运算符。适用于工作流决策取决于商品保质期的场景，例如质量控制、库存管理或合规检查。

## **功能：**

* **保质期验证：** 此卡片会根据指定条件检查商品的保质期。用户可以选择验证数据集中的**任意**商品或**所有**商品，并使用多种比较运算符设定条件。
* **商品选择：** 用户可以选择：
  * **任意商品：** 只要至少有一个商品符合指定的保质期条件，卡片就会触发。
  * **所有商品：** 只有所有商品都符合指定的保质期条件，卡片才会触发。
* **运算符：** 可使用以下运算符设定保质期条件：
  * **等于 (=)：** 检查保质期是否恰好等于指定值。
  * **不等于 (≠)：** 确保保质期不等于指定值。
  * **大于 (>)：** 确认保质期大于指定值。
  * **大于或等于 (≥)：** 确保保质期大于或等于指定值。
  * **小于 (<)：** 检查保质期是否小于指定值。
  * **小于或等于 (≤)：** 确保保质期小于或等于指定值。

## **用法：**

此卡片适用于质量控制团队、库存管理人员或合规专员，他们需要在继续执行后续操作或工作流之前，确保商品符合特定的保质期要求。

## **示例场景：**

* 用户将卡片配置为检查**所有商品**的保质期是否**大于或等于 30 天**。如果每件商品都符合此条件，工作流就会继续，从而确认所有商品的保质期足以支持销售或配送。

通过使用“保质期验证”卡片，组织可以执行保质期标准、维护产品质量，并确保工作流根据商品保质期条件准确运行。


---

# 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/items-have-shelf-life.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.
