3762241 - Multiattachment field marked as required does not validate during status changes in the Latest Workbench – Recruiting Management

In the New Workbench, mandatory Multiattachement fields are not getting validated allowing users to move candidates from one status to another without adding an attachment.

SAP SuccessFactors Recruiting Management

1. Configure a Job Application template with a field of type multiattachment (for example, Background check attachments) and set required="true" with appropriate write permissions
2. In the Legacy Workbench:
3. Change the Status field on the application and click Save: an error “Field is Required” is displayed and the status change is blocked.
4. Use Actions > Move to update the status: the candidate moves without validating the required attachment field.
5. In the Latest Workbench (UXR):
6. Change the Status field on the application and click Save: the candidate moves without validating the required attachment field.
7. Use Actions > Move to update the status: the candidate moves without validating the required attachment field.

By design, in the Latest Workbench, attachment files are added and modified in a separate "Resume and Documents" portlet (not in the Applicant Information portlet).

In the Latest Workbench this multi-step architecture means required-field validation for attachment fields is intentionally not executed during status change.
In the legacy workbench validation occurs only when updating the Status field and saving on the same page; the Move action does not validate required attachment fields.

This has been confirmed by Engineering that is expected behavior: required validation for multiattachment fields is not performed during status changes in the latest workbench, and it is also bypassed when using the Move action in the legacy workbench.

To ensure attachments are collected, add the required documents in the Resume and Documents portlet before performing any status change.

If validation at the time of status update is needed, use the legacy workbench and change the Status field directly, then click Save (this enforces the “Field is Required” validation path).
Avoid relying on the Move action to enforce required attachment validation.

latest workbench, uxr, legacy workbench, background check attachment, multiattachmentselection, required field, mandatory, status change, move action, validation, resume and documents portlet, applicant information, job application template, recruiting management, attachment validation, multiattachment. , KBA , LOD-SF-RCM-BCI , Background Check , Problem