> 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/then/document-field/set-to.md).

# 设置为

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

## **用途：**

此工作流卡片用于根据 **“Where”** 和 **“And Sections”** 中定义的条件，将文档中的指定字段自动设置为预定义的文本值。满足特定条件时，它可以确保字段填入一致的值，从而简化数据录入。

## **卡片组件：**

1. **字段名称**
   * **说明**：指定要更新为文本值的字段。
   * **详情**：如果满足 **“Where”** 和 **“And Sections”** 中的条件，所选字段将更新为指定的文本值。
2. **文本**
   * **说明**：定义条件判断为真时要设置到目标字段中的文本值。
   * **详情**：这可以是用户希望写入字段的自定义消息、状态或预定义值。文本应符合字段预期的输入格式（例如字母数字、日期或其他类型的文本信息）。

## **功能：**

* **条件评估**：系统会评估 **“Where”** 和 **“And Sections”** 中的条件：
  * 如果**两个条件都为真**，则执行 **“Then Section”** 中定义的操作。具体来说，目标字段（字段名称）将填入指定文本。
  * 如果 **“Where”** 或 **“And”** 部分任一条件为假，则不执行任何操作，字段保持不变。任一条件为假时，系统将完全跳过 **Then Section** 中的操作。
* **执行操作**：如果满足 **“Where”** 和 **“And Sections”** 中的两个条件，系统会自动将选定的文本值填入指定字段。如果不满足条件，则不会更改字段。

## **设置和配置：**

设置此卡片：

1. **选择字段**（字段名称），即要更新为文本值的字段。文档中的可用字段会列出供用户选择。
2. **指定文本值**，即条件为真时要写入目标字段的值。
3. 只有在 **“Where”** 和 **“And Sections”** 中的条件评估结果都为真时，才会执行此操作。

## **结论：**

**“Set Field to Text”** 工作流卡片提供了一种简便方式，可根据预定义条件自动将文本值填入特定文档字段。这可以减少手动数据录入，确保文档处理的一致性，是自动化工作流和提高效率的实用工具。


---

# 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/then/document-field/set-to.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.
