Candidate initial password issue

Stacey Doty

Is anyone experiencing issues with the initial candidate password not working? Our external candidates apply in Talemetry and then are passed to Infor. Once they hit Infor we send them a thank you for applying email with their user name and a generic password. We are having issues where some of our candidates are not able to log in using that initial password. We are not using security questions.

Legacy Contributor

Yes!  Having a nearly identical issue.  I it has something to do with the Talemetry interface not updating once a candidate changes how they use their name when applying.  I've seen this with candidates who use all caps then change to proper case, and even candidates using a different name (odd, I know).  Here is an example of what I have found:

The first time a candidate applies to a job they use all caps, e.g., BILL SMITH.  "BILL" is being sent to Infor and is establishing the actual system password, for example, "BILLxxxxx."  Subsequently, when Bill applies to another position, he uses proper case "Bill."  Although proper case "Bill" is correctly reflecting as his first name, all caps "BILL" is stuck in the initial password.  

In our case we send an email to a candidate once we make an offer.  We have a Job Offer email template that uses the Text Variable Replacement for {CandidateFirstName} and {InitialPassword}, and we provide a link for the candidate to login and view their offer. 

What is happening is the {CandidateFirstNam} and {InitialPassword} correctly reflect "Bill," but the actual password is "BILL."  So, the candidate is trying to log in using the password provided and it is not working, but if they use "BILL" then that works.  

I suggest going to "View Full Audit Log" and looking at the first "Create" action and looking at the "Name.GivenName."  This might be the actual password candidates should be using.  This has been the answer for us.

I hope this helps.  Keep me updated as I'd like to know if my theory is correct.