3809935 - Attachments added to a new application appear in other applications of the candidate - Recruiting

Attachment added on multiattachmentselection field type on the new application is being copied to the other application of the candidate that is using the same job requisition/Application template. 

SAP SuccessFactors Recruiting 

1. Apply to a new job requisition on the career site. 
2. Open and complete a new application and attach a document to a multiattachmentselection field. 
3. Save or submit the new application.
4. Open the other application that has already been submitted/completed.
5. Observe that the attachment added on the new application is visible on the other application.

This is an expected behavior. The multiAttachmentSelection field functions as a candidate-scoped mini document library, not an application-specific store. When a candidate uploads a document to this field, it is saved at the candidate level and becomes available for selection in all of the candidate’s applications. As a result, documents added via this field in one application are visible and reusable across the candidate’s other applications.

• Pre-population (candidate experience):
  • When the candidate opens Application 2, the field auto-populates with all documents in their candidate-level library, including those uploaded in Application 1.
  • This is not a candidate profile sync; it’s the field type’s built-in library behavior.
• Cross-application visibility (candidate view):
  • Any document uploaded to this field in any application is visible to the candidate across all applications on the career site.
  • This is by design: the underlying document library is shared at the candidate level.
• Recruiter view (application-scoped):
  • Recruiters only see documents that were explicitly selected for that specific application at the time of submission/snapshot.
  • This can make the recruiter view look “correct” while the candidate view seems inconsistent, but both are behaving as designed.
• Deletion behavior:
  • All applications reference the same candidate-level library entries.
  • Deleting a document from one application removes it from the shared library, causing it to disappear across all applications.
• Field location and scope:
  • Even if the field exists only on the Application template (and not on the candidate profile), storage is still candidate-scoped because of the field type’s library mechanism.
  • The field behaves as a shared store regardless of where it’s configured.

• Difference between multiattachment and multiattachmentselection fields
• 2865568 - Behaviour of multiattachmentselection fields from the Candidate Profile to the Application
• 3305948 - Documents attached in multiattachmentselection fields in the Candidate Profile are not synchronized to the Application

multiattachmentselection, attachment copied, duplicate attachments, additional documents, candidate application, job application, same job requisition, recruiting management, attachment field, synchronization, multiattachment, application form, document upload, RCM, attachments appearing across applications , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem