Symptom
OnInit Rules that refer to first-name or last-name fields on personalInfo portlet not triggering correctly since 1702 release.
OnInit Rules that refer to national id fields on nationalIdCard portlet are not triggered either.
Rule trace will show null values are being returned.
Reproducing the Issue
Configure an OnInit Business Rule to trigger on personalInfo/NationalID info that will check and pull values.
Cause
PersonalInfo node with "employee" type, personalInfo_employee, is causing the problem.
if this UI node type is enabled then the following can be impacted:
- Field Visibility
- Field Mandatory
- Business Rules
- Field Labels & Translations
Resolution
This is redundant configuration and once the personalInfo_employee node or nationalIdCard_employee node is disabled, the OnInit rules will trigger as they should.
The system does not expect a separate node for "employee" to appear in BCUI with "employee" type, as "employee" should be the parent node. The correct configuration is to have a standard layout (which would be displayed for employees) and a custom node only for dependents.
Although working previously, a code change in 1702 with regards to OnInit rule triggers brought this misconfiguration to the forefront.
See Also
2453207 - B1702 Personal Information Not Working as expected, ignoring 'required' or 'visibility' properties.
Keywords
1702 OnInit Rules personalInfo Null Value Rule Trace first-name last-name , KBA , LOD-SF-EC-PER-PRS , Personal Info - Config, Rules, RBP, UI , LOD-SF-EC , Employee Central , LOD-SF-EC-PER-NAT , National ID - Config, Rules, RBP, UI , Problem