When a candidate is forwarded from one requisition to another, the comments and attachments do not follow to that requistion. This is intended between recruiters who pass candidates between one requisition to another owned by different recruiters.
SuccessFactors Recruiting Management (RCM) - All versions
Reproducing the Issue
Forward a candidate from one requisition to another requisition. Make note of the comments and the attachments in the first requisition.
Its evident that comments have not followed over to the next requisition and so is the case with the attachment.
This is an expected behavior, we need to understand the way the data gets forwarded which is as follows.
When a candidate is added to a requisitions or forwarded directly, data gets populated from the last valid application of the candidate. The application from which information gets picked up is not the application from which the forward is done, but rather the latest application of candidate.
This application has to be the one in which the candidate has personally applied to ( not application he has been forwarded or added by recruiter ) .This is to make sure that the data that is forwarded has been viewed and reviewed by applicant.
Lets take an example of a candidate
If a candidate is forwarded from Requisition A to Requisition B but he has not yet applied to Requisition B and it is not his latest . This is why data from Requisition A is not forwarded to Requisition B . You can also see the notification in external candidate profile of this candidate as:
"Non Applicant - This candidate has been added to this job but has not yet applied for it."
Which signifies and justifies the above statement.
The comments and respective attachments have to be added again to the new requisition where the candidate has been forwarded, either by the candidate or by the user who has required permission to add and move the candidate in the candidate status pipeline.
Forward with data intact, Forward Candidate , KBA , LOD-SF-RCM , Recruiting Management , Problem