on ‎2014 Feb 13 1:26 PM
Dear All,
I am facing one illogical issue.
Suppose one external candidate has created their own profile. After that he has applied against one published job. But he is able to change own data and its getting changed in applied job (candidacy). It should not get change.
Recruiter is processing & doing activities against all selected candidates. So at this time candidates should not be able to change their data because they already applied against job.
When an external candidate is changing their own data after login, it’s not only getting changed in object type candidate but it is also getting changed in object Candidacy. It means Recruiter, who has selected candidate according to their education,experience,etc doesn't make any sense and he can process wrong candidate.
So my concern is how to restrict those candidate data who has already applied against a job.
I think i have explained my issue correctly.
Please guide me and suggest standard solution for this.
Best Regards,
Deepak
Request clarification before answering.
Dear Deepak,
it is perfectly fine that a candidate can change his profile as he can apply more than ones in parallel.
He also might be asked to update his profile if he forgot something.
If you have problems for legal cases because in the end you rejected someone and he is complaining and you want to proof the very certain profile at time of application, you can use the audit trail functionality within the recruiting administrator.
he can recall frozen profiles which is written by standard workflows whenever the application status is changing.
For the normal working process the recruiter can only call the live profile.
BR
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.