> 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/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.md).

# 申請ワークフローの実行順序を設定する

アプリケーションのワークフローの順序を並べ替えることで、これらのワークフローが実行される順番を制御できます。

複数のワークフローに重複する条件がある場合、その順序によって結果が異なることがあります。たとえば、 *米国外のパートナーを拒否する* ワークフローと *すべてのクリエイターを承認する* ワークフローは、米国外にいるクリエイターに対して矛盾する結果を生み出す可能性があります。自動承認ワークフローが最初に実行されると、申請は承認されます。自動拒否ワークフローが最初に実行されると、申請は拒否されます。

1. 左側のナビゲーションメニューで、 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[エンゲージ]** → **パートナー** → **自動化** → **Workflows**.
2. ワークフロー画面で、 **申請** タブを選択します。
3. 右上隅で、次を選択します **ワークフローの並べ替え**.
4. 次の *ワークフローの並べ替え* モーダルで、ドラッグ＆ドロップ機能を使ってワークフローの順序を変更します。
5. 選択してください **保存**.

   * これで、アプリケーションのワークフローは新しい順序に基づいて実行されるはずです。

   <div data-with-frame="true"><figure><img src="https://1458456015-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/ja/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.
