Off Limits Policies Successful Candidate Withheld Use Case

Below is a use case that would apply if you want a candidateClosed to not be considered off limits even though they have been assigned to a jobClosed. This is typically used when tou want to prevent a candidate from being flagged as Off Limits. This will prevent the Off Limit icon/information confirming that the Candidate has been assigned to a job popup from coming up.

Use Case

Trigger When a user updates the Withheld field on the Closing ReportClosed to False, this triggers the creation of the Off Limits policy. The off limits constraint is enforced.
Main Flow
  1. Candidate C1 is placed on Job J1 for Account A1.
  2. A Closing Report is created.
  3. Candidate C1 is not Off Limits as a consequence of any Successful Candidate Off Limits policy.
    • No Successful Candidate Off Limit policy is created for the Successful Candidate.
Exceptions Candidate C1 is not Off Limits as a consequence of any Successful Candidate Off Limits policy for as long as the Withheld checkbox is selected.
Assumptions In the Withheld case, creating the Closing Report does not close the Job. Only when the Withheld checkbox is deselected will the rest of the Job close out.
Notes

To ensure that the Successful Candidate (and any other advanced-stage candidatesClosed) remains protected by the Off Limits constraint while the Successful Candidate Off Limits policy is Withheld, please leverage ATS Stage Off Limit policies.

For more details on this policy, see Off Limits Policies: ATS Stage.

 

Activity Diagram

Next Steps

To configure the Off Limits Successful Candidate Policy, see the Successful Candidate Policy Configuration section of Off Limits: Configuration Guide.