Symptom
The issue happens when below configuration and replication steps are met.
- The parent custom MDF has a Composite association to a child object. On the association's details page, a condition can be configured based on a field value defined in the parent object. For example, set the condition field to cust_A, which is a yesNo picklist field, and the child object will appear when the cust_A value is yes.
- Then create a Configuration UI for the parent object, give a special label for the child object, and set all child object's fields to be mandatory.
- After that, configure a hire template and add the MDF UI as mentioned above.
- When adding a new employee using the hire template, in the MDF block, choose No in the cust_A field. According to the condition setting, the child object will not appear. Save this as a draft.
Now, go to Manage Pending Hire > Draft, open the test user's page using the same template. Go to the MDF block and change the value in the cust_A field from No to Yes. The child object appears, but the label is not the one configured in the Configuration UI and all fields are not mandatory.
This issue also occurs in Manage Pending Hires < Onboarding.
Environment
SAP SuccessFactors Employee Central
- Hire Template
- Manage Pending Hires
SAP SuccessFactors Onboarding 2.0
- Manage Pending Hires
Resolution
This is a known issue.
The development team is currently working on fixing the issue, but the date for the fix has not been confirmed.
The KBA will be updated once the fix is reday.
Keywords
WEF-163024, COD0364251 , INC10859613, INC11747071, INC11747300, manage pending hires, draft, onboarding, draft(onboarding), custom MDF, attribute, label , KBA , LOD-SF-EC-HIR-CHW , Configurable Hire Wizard , LOD-SF-OBX-EC , Integration EC - MPH, Hire , Known Error