> 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/task/create-a-new-task-and-assign-it-to-procurement-group.md).

# 创建新任务并将其分配给采购组

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

## **用途：**

\*\*“为采购组创建任务”\*\*工作流卡片会创建一个新任务，并根据配置动态分配给指定的采购组。任务可以设置不同的优先级，还可以选择发送电子邮件通知，告知该组有新任务。此卡片可根据工作流条件提醒正确的团队。

## **卡片组件：**

1. **标题**
   * \*\*说明：\*\*指定任务的标题。
   * \*\*详情：\*\*此字段用于标识所创建的任务，并提供简洁的标题，便于快速识别。
2. **描述**
   * \*\*说明：\*\*提供任务的详细信息。
   * \*\*详情：\*\*此字段用于说明任务目标，以及必要的背景信息或操作说明。
3. **优先级**
   * \*\*说明：\*\*定义任务的紧急程度。
   * **选项：**
     * \*\*高：\*\*任务需要立即处理。
     * \*\*中：\*\*任务很重要，但不紧急。
     * \*\*低：\*\*任务可以稍后处理。
4. **组名称**
   * \*\*说明：\*\*指定要将任务分配给哪个采购组。
   * \*\*详情：\*\*此字段用于指定负责该任务的采购组，确保任务分配给正确的团队。
5. **电子邮件通知**
   * \*\*说明：\*\*设置是否向已分配任务的采购组发送电子邮件通知。
   * **选项：**
     * \*\*True：\*\*向采购组发送电子邮件通知。
     * \*\*False：\*\*不发送电子邮件通知。

## **功能：**

* **条件评估：**\
  只有当 **“Where”** 和 **“And Sections”** 均评估为 true 时，此卡片才会执行操作。
* **创建任务：**\
  此卡片会创建一个新任务，并将其分配给“组名称”字段中指定的采购组。任务将包含指定的标题、描述和优先级。
* **电子邮件通知：**\
  如果电子邮件通知选项设为 true，系统会向采购组发送电子邮件，告知他们有新任务。

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

* **定义任务详情：**\
  输入任务的标题、描述和优先级。
* **选择采购组：**\
  选择负责该任务的采购组。
* **启用电子邮件通知：**\
  指定创建任务后是否向该组发送电子邮件通知。

## **结论：**

“为采购组创建任务”工作流卡片可确保任务自动分配给合适的采购组，并设置相应的优先级。此卡片还可以通过电子邮件通知该组及时处理任务，从而提高工作流效率和任务管理水平。


---

# 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/task/create-a-new-task-and-assign-it-to-procurement-group.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.