3730236 - Foundation Object (FO) / Generic Object (GO) validation does not work during Onboarding steps - Onboarding

The Foundation Object (FO) / Generic Object (GO) validation doesn't work during Onboarding steps, for example: New Hire Data Review step, Final Review step. 

1. Initiate onboarding for a new hire.
2. Navigate to the New Hire Data Review step.
3. Enter an inactive job classification code for the candidate and submit the New Hire Data Review successfully.
4. Go to Manage Pending Hires page, click on submit button, validation triggered:

   The selected JobClassification xxxxx is inactive on DD/MM/YYYY. You can either validate the JobClassification on Manage Data page or you can select another JobClassification.

This is expected behavior: validations based on Foundation Object (FO) / Generic Object (GO) are not evaluated during the Onboarding steps.

1. Create an onSave business rule for the Onboarding Job Information to perform the required validation (for example, check that the selected Job Classification is active on the effective date).
2. Configure the rule so that it displays an appropriate validation message when the condition is not met.
3. This rule needs to be added at the corresponding entity on Admin > Manage Business Configuration (jobInfo)
4. Test by initiating onboarding and verifying that the rule validates the data during the Onboarding step.

Refer to: 2997223 - FO/GO invalid external code in EC portlets

3287521 - How to Add Validation Messages - Onboarding

onboarding, new hire data review, job information, validation rule, onSave rule, inactive external code, FO, GO, job classification, validation not working, expected behavior, ECT_service_layer_HRIS_ERROR_INACTIVE_EXTERNAL_CODE_GO, EC portlets, HRIS, data validation, HrisGenericObjectsValidator , KBA , LOD-SF-OBX-NHR , Onboardee Data Review , Problem