ATS v2: Interview Attendee Interviewer Configurations Logic

• If multiple checkboxes are selected in the Interviewer Usually the client/hiring manager taking part in a Job interview. A recruiter can also be an Interviewer Configurations records (given that the selection is supported), the AND logic is applied.
  • For example, if Contacts A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact). with Job Roles and Users as Team Members checkboxes are both selected for the Internal Interview The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. action, the Contacts with Job Roles and Team Member Users will be retrievable as Interviewers.
• Selecting the Active check-box on two different of these metadata type (.mdt) records turns the feature into a switch, enabling the Interviewer/s' lookup logic as defined in this Custom Metadata Type.
  • Enabling this logic does disable out-of-the-box behaviors. When switching to this configuration, the following changes will take place:
    • Interviewer/s' lookup is not pre-populated in any scenario.
    • No option to create a New Contact directly from the Interviewer/s’ lookup field on Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. Schedules.
    • Searching by typing a few letters or using suggestions will only retrieve the Users or Contacts that match this custom metadata type configuration.