We would like the full configuration flexibility (Required/Optional/Off) for all fields which are not mandatory for the creation of a Candidate record. Especially the Candidate Email field.
We use the new Career Site and the Candidate Application Form. It looks great and it is very efficient when publishing new Job Openings. We have recently migrated from US DC to EU DC and we are recreating our setup. We have run into problem since it looks like we can no longer disable the Candidate field Email from the Candidate Application Form.
We have previously expressed our concern with allowing new applications updating the existing records without any control, see
Our solution to this has been to use a dummy email field on the Candidate record visible on the Application Form. Since we have no Email field, a new temporary Candidate record is always created. The creation of the temporary record triggers a Verification Email to the Candidate dummy email address with a link to a "Reconfirmation and Consent Form" created in Zoho Forms. The link to the form contains the information submitted by the applicant in the Application Form via the Forms' Field Alias mechanism. We use the Zoho Forms form to capture more information (sometimes the Candidate is submitted by a third party) as well as a mechanism to capture and document a more granular consent than the consent solution in Zoho Recruit. The Zoho Forms form integrates with a Zoho Recruit Custom Module for Consents. The creation of the Consent record triggers a Deluge script checking if the created temporary Candidate record already exists in Zoho Recruit. If it doesn't, the script upgrades the temporary record to a real record updating the Email field with the dummy email. If the dummy email already exists and names etc are the same as before, the application is added to the existing record and the dummy record is deleted. If there is a conflict, we trigger manual intervention via an email alert.
For this to work we need to disable the Email field from the Career Site's Candidate Application Form. There might be a workaround to hide the Email field on the Candidate Application Form, but in that case it is mandatory to set a default email address. Why?? Wouldn't this merge all new Candidate records to one and same record??. A Deluge script trigged by the creation of the temporary record could potentially erase the default email address but it seems to be a rather clumsy solution compared to enable OFF also for the Email field. Or take away the mandatory default address requirement. If you enable the OFF alternative for Email, please do the same for Mobile.