Troubleshooting for Managing Candidates

This section covers the following issues:

Hiring a Linked Former Employee Is Creating a Duplicate Employee Number

When a recruiter links a candidate to their former employee record and hires the candidate in Recruiting, the system updates their original employee record and employee number rather than creating a new one. In order for the system to update the existing employee record instead of creating a record, the following conditions must be met:

You must select the Enable SSN Validation checkbox in the Employee section of the Properties tab in System Admin > Client Properties.
The employee's SIN/SSN number, last name, and country need to be the same as their original employee record.
There must be an employment status reason with the reference code of "REHIRE" in HR Admin > Employee Status Reason. When rehiring the employee, the system checks for an employee status reason with the reference code of "REHIRE". If the system cannot find it, the process doesn't work.

Internal Candidate Status Is Not Updated by Questions in the Job Application (For Example, Auto-Decline)

The auto-trigger candidate status feature is available for external candidates only, and not internal candidates. This applies for all candidate statuses, including decline. You can update only an internal candidate's status manually, which is done in Recruiting > Job Requisitions, in the Candidates tab.

Candidate Phone Numbers Aren't Saved

There must be "Mobile" and "Home" entries in HR Admin > Contact Information Types. These entries are required for candidate phone numbers to be saved to Dayforce. This applies to phone numbers added by recruiters in Recruiting > Talent Community, or by candidates when they apply for jobs from third-party sites such as Indeed.

Candidate Profile Print-Out Is Not Formatted Properly

The Recruiting module doesn't support the browser print function (for example, when a user clicks File > Print or presses Ctrl+P in Internet Explorer, the candidate profile is printed in an incorrect format). Therefore, you should always print the candidate profile using the Print button at the top of the candidate profile.

Hire Form Not Displayed in the Form Submissions List

In the Form Submissions list (in People, in the Forms screen), only forms that your user role is assigned access to in the People feature are displayed.

For example, if you have access to the Candidate Hire form in the Action drop-down list in People, you will be able to see that form in the Form Submissions list for employees as well.

To enable access to a form in the Action drop-down list of People:

Go to Workflow Administration > Role Privileges and click Add.
Do the following:
- In the Parent Feature column, select HR Profile Forms List.
- In the Form column, select the form that you want to display.
- In the Workflow column, select the workflow that you want to associate with the form.
- In the Role column, click the field to open a dialog box in which you can define which roles will have access to the form. Click OK to close the dialog box.
Click Save.

Existing Questionnaires Are Not Copied Over When Assigning Candidates to a New Requisition

Questionnaires associated with the candidate’s original job application aren't copied over when you assign them to a new job requisition. This is because each job posting uses an application template that was created specifically for that posting, and the questions and scoring from the original application don't directly apply to the newly assigned job requisition. Candidates can have multiple questionnaires attached to their profile, but only the questionnaires for the specific job requisition are displayed.

If you want to view the candidate’s existing questionnaires, go to the job requisition to which they originally applied.

Workflows for Candidate Status Notifications (For Example, Decline) Are Failing

In Workflow Administration > Workflow Designer, verify that the quotation marks used in the Create Expression dialog box for the condition node are straight quotes rather than curly quotes (or, "smart quotes"). Curly quotes can result when you type the expression in programs like Microsoft Word and then copy and paste it to the Create Expression field. Including curly quotes will cause the workflow to end in error.

Incorrect:

<<CandidateCommunicationData.JobPostingApplicationStatusXrefCode>> EQUALS “DECLINED”

Correct:

<<CandidateCommunicationData.JobPostingApplicationStatusXrefCode>> EQUALS "DECLINED"

It's recommended that when editing expressions, you use a text editing program such as Notepad++ where straight quotes are used.

Workflows for Candidate Hire Forms That Allow Attached Documents Are Failing

Attaching documents to the Candidate Hire form isn't supported.