Candidate was able to submit the application after the posting expiry date.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental
SAP SucessFactors Recruiting Management
Reproducing the Issue
- Set the expiry date of a job posting and post the requisition
- Candidate starts to apply for this position
- Candidate saves their incomplete application to resume at a later stage
- Meanwhile the posting expires
- Candidate is still able to resume the application process and submit their application even after the posting has reached its expiry date
The candidate started to apply to the requisition and just saved the application, however they did not submit it.
If the private posting date has not expired and if it is still valid, then the saved application can be submitted within that time, even though the internal/external posting is expired.
The job requisition has been posted and the Internal Posting and the Internal Private Posting dates have been set.
The candidate starts to apply for the position but saves their incomplete application to resume at a later stage
Now the internal job posting has expired, however the internal private posting is still in date.
At this point, the candidate will still be able to submit their previously saved application.
Please note that the screenshots above apply to the internal postings. This scenario applies to external postings also.
Best practice is to ensure the private postings have the same expiry date as the corportate/internal postings unless there is a valid business reason not to.
It is expected behavior that if these dates are different, the candidate will be able to submit their application after the posting has been removed.
private posting; expiry date; application; submit; candidate , KBA , LOD-SF-RCM , Recruiting Management , Problem