> 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/action/ai-calculation-for-cost-increase-surcharges.md).

# 价格上涨附加费的 AI 计算

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

## 用途：

\*\*“价格上涨附加费的 AI 计算”\*\*工作流卡片使用 AI 根据成本上涨自动计算附加费金额。它可确保附加费计算一致且准确，从而简化工作流并减少人工操作。

## 卡片组件：

* **成本上涨系数**
  * **说明：** 应用于基础成本以计算附加费的乘数或百分比。
  * **详情：** 根据成本上涨幅度确定附加费金额（例如，系数为 1.10 表示上涨 10%）。
* **基础成本字段**
  * **说明：** 包含用于计算附加费的原始成本值的字段。
  * **详情：** 该字段会自动选取，或在工作流中定义，以便在计算时参考。
* **附加费字段**
  * **说明：** 用于存储 AI 计算出的附加费金额的字段。
  * **详情：** 此字段显示计算出的附加费，供后续处理或报告使用。

## 功能：

**条件评估：**

* 只有当 **“Where”** 和 **“And Sections”** 条件都评估为 true 时，此卡片才会激活。
* 如果任一条件评估为 false，则不会执行附加费计算。

**AI 驱动的计算：**

* 系统将**成本上涨系数**应用于**基础成本字段**，以计算附加费。
* 计算结果存储在**附加费字段**中，确保后续工作流步骤可以使用该结果。

## 结论：

\*\*“价格上涨附加费的 AI 计算”\*\*工作流卡片可根据成本上涨情况自动应用附加费。该卡片利用 AI 确保计算精准、一致，省去人工计算，提高效率，并支持自动化工作流中的准确成本管理。


---

# 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/action/ai-calculation-for-cost-increase-surcharges.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.
