Main Use Case for Successful Candidate Placement Off Limits Policy

Below is a use case that would apply in most instances when a candidateClosed is placed in a jobClosed and you want the Off Limit icon/information popup that confirms the Candidate has been assigned to a job.

Trigger Closing report is saved in the Org where a Successful Candidate Off Limits Policy has been created.
Main Flow
  1. Candidate C1 is placed on Job J1 for Account A1.
  2. A Closing ReportClosed is created.
  3. If the Successful Candidate feature is enabled in the Org, a Successful Candidate Off Limits Policy is created when the Closing Report is saved.
  4. Candidate C1 becomes Off Limits on Closing Report Created Date .
  5. The candidate stays Off Limits for the period defined by Start of AssignmentClosed plus the Duration.
Exceptions
  • Events: The only event that could cause the Successful Candidate to no longer be Off Limits before the policy expiry date is a change in their employment status (i.e., the Candidate no longer works for the Job’s Account or any other Account in the same hierarchy).
    • Logic configuration options are available to apply checks to the Job’s Billing Account.
  • Manual: It is possible for the policy to be manually disabled by internal users.
Notes
  • The Successful Candidate Off Limit policy logic only considers the Candidate that has been assigned to the Job.
    • Any off limit requirement for any other Candidate applied to the Job but not placed should be covered by other Off Limits policies and configured separately.

 

Activity Diagram

Next Steps

It will also help you to understand what the other use case is, for this see Off Limits Policies Successful Candidate Withheld Use Case.