Using eligibility groups within automations for quick actions

If your organization uses eligibility groups, then you may have multiple automations for each quick move action. For example, you may have one automation for the quick move action of Yes for the eligibility group of internal candidates and another automation for the quick move action of Yes for the eligibility group of external candidates.

It is important to consider the sequence of how your automations are configured. For example, if you have a quick move action of Yes with no eligibility group, then when Advance Candidate is clicked on a candidate job application all candidates are moved to a specified workflow step. In this case, the system ignores the two other automations for the quick move actions that are based on eligibility groups since the Run Upon is sequenced after the first automation with no eligibility group.

If you want the eligibility groups to be run first, then you must specify the Run Order setting of those automations to occur first. For example, the quick action of Yes runs first for the eligibility group of external candidates and move those candidates to the specified workflow step. Second, the automation for the quick action of yes for the eligibility group of internal candidates runs. Finally, the automation for the quick action of yes for all other candidates, because there is no eligibility group, runs.