Before You Begin: You must always add this condition node after the condition node that checks for status. The workflow should check whether a status occurred before checking if it occurred for an internal or external candidate. Placing it before the node that checks for candidate status can cause workflows not to run. See HR Event. While you must not place this condition node before the condition node that checks for candidate status, you can place it before or after other condition nodes that are described in this document.
You can add a condition node to your workflow that checks whether a status update occurred for an internal or external candidate. This allows you to configure a workflow to send a separate notification with different content to internal and external candidates, or to exclude either internal or external candidates from receiving a notification. Adding a condition node that checks whether a candidate is internal or external is optional. If you don’t add it, the workflow sends a notification both to internal and external candidates by default.
Important: If your organization requires a separate internal and external notification for the same candidate status (for example, “New”), don’t create separate workflows. Using separate workflows for the same candidate status can cause workflows not to run. Instead, you must combine all notifications for the same status into a single workflow, as is shown in this topic.
Example 1:
In the following example, the workflow is configured to send a separate notification to internal and external candidates when they apply for a job. An additional condition node (selected below) was added after the condition node for automatic or manual status. If the candidate is internal, the true connector from the node leads to a notification for internal candidates. If the candidate is external, the false connector from this node leads to a notification for external candidates:
If you want the workflow not to send a notification to an internal candidate, you can link the true response from this condition node directly to the end node, and vice versa if you want to send a notification only to external candidates.
Example 2:
In the following example, the workflow is configured to send decline notifications to internal and external candidates:
The steps in this workflow are described as follows:
- The workflow begins by checking whether the "Declined" status occurred. If this is true, it continues to the next condition node, which checks whether the candidate was internal or external.
- If the candidate was internal, the workflow continues to the notification for internal decline.
- The condition that checks for internal and external candidates was added before the condition that checks automatic and manual status changes because automatic decline is available only for external candidates. Internal candidate status cannot be updated as a result of a screening question. When an internal candidate is declined, it's always manual, and therefore the workflow can go directly to the notification for decline.
- If the candidate was external, the workflow continues to the condition node for manual and automatic status updates.
- If the status update for the external candidate was manual, the workflow continues to the notification for external manual decline.
- If the status update for the external candidate was automatic, the workflow continues to the routing and decision nodes for time delay, and finally to the notification for external automatic decline.