> 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/any-value-of.md).

# 任意值

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

## **用途：**

此 DocBits 卡片用于验证表格中特定列的任意值是否与给定的正则表达式模式匹配。只要该列中有一个条目匹配此模式，工作流就会继续执行，因此非常适合通过单个匹配项触发流程后续步骤的场景。

## **功能：**

* \*\*正则表达式模式验证：\*\*此卡片会检查表格指定列中的任意值是否与给定的正则表达式模式匹配。如果该列中至少有一个条目满足条件，卡片就会触发并允许工作流继续执行。
* \*\*运算符：\*\*用户可以定义列并指定正则表达式模式。可用条件包括：
  * \*\*匹配正则表达式模式：\*\*验证指定列中至少有一个值与正则表达式模式匹配。
* \*\*表格和列选择：\*\*用户可以指定要检查正则表达式模式匹配情况的表格和列。

## **用法：**

当表格中的数据需要进行特定匹配时，此卡片尤其有用，例如验证电子邮件地址、发票编号或产品 ID。它能确保只要有任意相关条目与定义的模式匹配，工作流就会继续执行，而无需检查每个条目。

## **示例场景：**

* 用户将此卡片设置为检查“Customers”表格中“Email Address”列的条目，并使用用于匹配有效电子邮件格式的正则表达式模式。如果该列中至少有一个电子邮件地址与此模式匹配，卡片就会触发工作流的下一步，确保系统处理有效条目。

通过使用“Regex Pattern Matching”卡片，组织可以根据动态的模式验证自动执行工作流，从而简化流程，并确保只有相关条目才能触发后续操作。


---

# 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/any-value-of.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.
