> 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/workflow-best-practices-and-faqs.md).
# 工作流最佳实践与常见问题
参加 PXA 课程
{% embed url="" %}
## 工作流常见问题
如何跟踪已接受的申请？
若要跟踪工作流规则已接受了哪些合作伙伴， [创建一个合作伙伴组](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md) 为每个工作流，并在 [创建或编辑工作流时将已接受的合作伙伴分配到该合作伙伴组](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md).
设置工作流时，哪些条件组合比较好？
这取决于您的业务需求。以下是两组配合良好的条件：
1. **商业模式、合作伙伴规模和合作伙伴所在国家/地区**
使用这些条件，您可以指定希望合作的合作伙伴规模和类型，以及他们应位于何处。
{% hint style="info" %}
**示例：** 比如您想与英国的大型内容发布商合作，您可以将条件设置如下。
{% endhint %}
2. **模板条款和合作伙伴国家/地区**
使用这些条件，您可以指定希望以哪些条款与特定国家/地区的合作伙伴合作。
{% hint style="info" %}
**示例：** 比如您想与位于美国的优惠券合作伙伴合作。
{% endhint %}
{% hint style="success" %}
**注意：** 包含 **分配组** 和 **处理申请** 操作类型。
{% endhint %}
如何撤销工作流已处理的合作伙伴申请？
如果工作流已接受或拒绝了某个申请，而您想要不同的结果，请选择 **查看决定** 在该申请的 *已处理* 选项卡中的 *申请* 屏幕。您可以接受之前被拒绝的申请，或使之前被接受的申请的合同到期。
要查找某个特定工作流处理过的申请，请使用 **组** 和 **状态** 筛选条件。
请参阅 [更改已处理申请的决定](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/process-partners-in-bulk-and-reverse-rejections.md#change-a-decision-on-a-processed-application) 用于这些步骤。
## 工作流创建最佳实践
以下是如何最佳利用工作流来处理合作伙伴申请的提示：
* 使各个工作流彼此互斥。您可以通过确保不同工作流之间的条件不相互矛盾来实现这一点。如果存在相互冲突的工作流规则，将使用最近更新的工作流中的操作。
* 当您刚开始使用工作流时，让工作流将已处理的合作伙伴添加到一个 [独立组](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md) 这样您就可以轻松在 [申请](https://app.impact.com/secure/advertiser/engage/contracts/activity/adv-manage-pending-public-ios-v2-flow.ihtml) 屏幕上，借助 *组* 筛选器。
* 保持前几个工作流简单且宽泛，然后随着您对工作流的使用越来越熟练，再逐步使其更精确。
---
# 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/workflow-best-practices-and-faqs.md?ask=&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.
