Candidate Record Update Strategy

When a new resume is parsed for a candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. already in your Org, if the resume contains a "new" language (a language that was not mentioned in previous resumes), then a new language record is created. If the resume contains the same language as an already existing language record for that candidate, the update strategy comes into play.

As part of the initial implementation System Administrators can choose one of two update strategies:

• Override: When a resume is parsed, if it has a different language level than the existing Language record, the Proficiency Level field updates. The previous value is overridden, so if a recruiter has manually entered this information, parsing the resume will override that value.
  

  Parsed Data	Expected Result
  Resume has the same Language + same Language Level	No changes
  Resume has the same Language + different Language Level	Proficiency Level field is updated with the new level
  Resume has no data for that Language	No changes (This is an exception to the Override logic to preserve data.)

• Do Nothing: If the new resume has a different language level for an existing language record, the field does not update. This second option is provided in case the business requires that any updates made manually by recruiters take precedence over data parsed from a resume.
  

  Parsed Data	Expected Result
  Resume has the same Language + same Language Level	No changes
  Resume has the same Language + different Language Level	No changes
  Resume has no data for that Language	No changes