Hi experts,
I'm trying to understand the affects of requisitions and the process of them being set "To be deleted" and also the result of what happens to the corresponding ND, NE objects and relationships.
If a requisition is set to the status "To be deleted" AND after the retention period has expired, what is the best practice for dealing with these expired requisitions? I don't understand the lifecycle of a requisition in E-Recruiting.
Should requisitions go from Released > Closed > To be deleted?
Should a requisition that was filled by a candidate only be set to "closed" and never set "to be deleted"?
The issue we've encountered is a recruiter will release the requisition, process candidates through the activities, close the requisition, then once the position is filled, they will set the status "to be deleted". Based on the T77RCF_LAWPERIOD we keep the requisitions for two years. Once the two year mark hits, the ERecruiting Administrator could delete those requisitions that exceeded the retention period.
Now, once the Erec Admin deletes the requisition, the NB record ceases to exist. However, there are still lingering NE and ND objects and relationships that are orphaned, because there is no requisition anymore.
My assumption is either:
Requisitions that have had candidates should never be set to status "To be deleted" only to "closed".
OR
Requisitions deleted should be cleaning up the associated ND and NE objects and relationships and it's broken.
We are running into issues where candidates are applying to requisitions, but are receiving a generic "Internal error" message on the portal (which I haven't researched yet). It seems once I clean up the orphaned ND and NE objects and relationships, the errors stop.
Regards,
Garrett Meredith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.