Okay, I see what you were saying now, sorry I misunderstood.
On the HR case table, you can find a UI policy named Show HR service fields on load, in the script part of this UI policy setServiceDisplay function controls the visibility of the HR Service fields. [child and parent fields]
Counter attacking this UI policy, another UI policy named Hide HR service fields and related lists is responsible for Hiding the HR Service fields. [It only takes parent HR service fields, not the Child]
Use case 1: if you create the fields on Child case Tables, the field never gets hidden
1. created a custom column test1 to the HR workforce Admin Case table,[child table]
2. Configured the Service Table fields in the HR Service with test1 field
3. test1 field is VISIBLE on the HR workforce Admin Case table when I open it.[No UI policy to hide it as UI policy:Hide HR service fields and related lists only hides Parent table fields]
Use case 2: if you create the fields on Parent case Table, the field gets hidden and displayed properly
1. created a custom column test2 to the HR Case table,[parent table]
2. Configured the Service Table fields in the HR Service Without test2 field
3. test2 field is HIDDEN on the HR workforce Admin Case table when I open it.[UI policy:Hide HR service fields and related lists]
4. Configured the Service Table fields in the HR Service With test2 field
5. test2 field is VISIBLE on the HR workforce Admin Case table when I open it.[UI policy:Show HR service fields on load]
Something Silly: check the Form layout to see if the fields are configured to exist on the form in the first place.
Thank you,
Aman Gurram
