> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.md).

# 设置申请工作流执行顺序

通过重新排序您的应用工作流，您可以控制这些工作流的运行顺序。

当多个工作流具有重叠条件时，它们的顺序可能会导致不同的结果。例如，一个 *拒绝美国境外合作伙伴的* 工作流和一个 *接受所有创作者的* 工作流，可能会对位于美国境外的创作者产生相互冲突的结果。如果自动接受工作流先运行，申请将被批准。如果自动拒绝工作流先运行，则申请将被拒绝。

1. 从左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **合作伙伴** → **自动化** → **工作流**.
2. 在“工作流”页面中，选择 **申请** 选项卡。
3. 在右上角，选择 **重新排序工作流**.
4. 在……上 *重新排序工作流* 模态框，使用拖放功能重新排序您的工作流。
5. 选择 **保存**.

   * 您的应用工作流现在应根据新的顺序执行。

   <div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FZduOkxAUPS2Bsu2vPiIK%2FUntitled%20design.gif?alt=media&amp;token=1fe1b85a-b0f4-42cf-af6b-08e20946289a" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.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.
