Background Data is updated in Candidate Profile but not updated in Background section in Application

[Gi]

Hello,

There is a KBA that states candidate details have to be completed prior to Recruiter clicking into Application otherwise it will not feed over but when the candidate is asked to complete these details after Recruiter review, it is not updating in the background section of the Application page

In speaking with our support partner, they were suggesting an automation intervention by creating an integration in Integration Center which uses SF backend APIs which can automatically update the Background portlet in Application page however the cost is astronomical.

I wanted to see if any other companies are dealing with this issue and what their workaround is.

Thanks.

[RohitMohite]

Hey Gi Explorer,

[RohitMohite]

Hi @Gi ,

PFB note from implementation guide:

Problem Stmt: There are few fields on candidate profile which are not visible to Quick Apply applicant. And at later stage the candidate is entering the data on candidate profile but same is not helping to reflect it over job application.

Proposed Solution:
1) Create a new dedicated JRDM and Job Application template for Quick Apply

2) Include the affected fields in newly created Job Application Template

3) Hide the newly included fields from step 2 using Multi-stage Application

4) Identify the point/status from the talent pipeline to ask for input from candidate against fields included in step 2

5) Make the fields visible to Candidate and Recruiter at this stage

I hope this approach will be helpful for you.

Thanks.

[Gi]

Thanks Rohit. We will explore this alternative solution since we dont have a seperate template for quick apply at the moment. Appreciate your assistance.

[Gi]

Hi @Rohit- can you please check your inbox? i sent you a message privately. Thanks.

[RohitMohite]

Hey @Gi ,

Got it,

Since you have enabled Quick Apply and mentioned fields are part of candidate profile, the mentioned fields are not visible upfront to candidates.

It is always recommended to use different job application template for "Quick Apply" requisitions. If you are already having dedicated application template for "Quick Apply" applicant, then I would suggest to migrate the fields to candidate application template and make them visible at later stage for candidate during hiring process.

This way, the data would also get captured by avoiding to collect those at the time of application itself.

I hope this workaround would assist you.

Thanks,

Rohit

[Gi]

Hi RohitMohite-the mentioned fields are part of candidate profile which they can access upfront when creating their account but we did not make those fields required. Under manage templates, we have Candidate Profile template, Job Application template. Are you suggesting we have one additional one called Quick Apply? I am trying to understand what you are describing. Is there a KBA tied to this?

[RohitMohite]

Hey @Gi ,

It is best practice for candidate to complete all the essential fields prior to submission of job application. However, I would suggest a potential solution.

You could include the respective fields again in the Job Application template with the same field ID's which were used in candidate profile. I suspect, since the field ID will be same in both templates, it will assist in making data visible on job application page.

Thanks,
Rohit

[Gi]

Thanks for your response. We enabled quick apply and late stage application to avoid candidate having to be required to complete those fields upfront to lessen time spent applying to job. Recruiter wants to review those fields prior to interview step if candidate ends up completing those fields after they quick apply. Aside from the API integration and making these fields required upfront, any other solution?

[RohitMohite]

Hey @Gi , Got it, Since you have enabled Quick Apply and mentioned fields are part of candidate profile, the mentioned fields are not visible upfront to candidates. It is always recommended to use different job application template for "Quick Apply" requisitions. If you are already having dedicated application template for "Quick Apply" applicant, then I would suggest to migrate the fields to candidate application template and make them visible at later stage for candidate during hiring process. This way, the data would also get captured by avoiding to collect those at the time of application itself. I hope this workaround would assist you. Thanks, Rohit

[Gi]

Hi RohitMohite-the mentioned fields are part of candidate profile which they can access upfront when creating their account but we did not make those fields required. Under manage templates, we have Candidate Profile template, Job Application template. Are you suggesting we have one additional one called Quick Apply? I am trying to understand what you are describing. Is there a KBA tied to this?