- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2018 09:29 AM
I am trying to display fields for an HR service on the generated record by adding said fields to the HR Service record in the "HR Service Additional Information" tab and the "Service table fields" field. I am doing so in following step 3 in this Community answer, but the fields are not showing on the generated record.
Here's my "HR Service Additional Information" tab for the HR Service.
Yet when I look at the case this service generated I'm not seeing these fields. What do I need to do to get these to show?
Bottom of form:
Solved! Go to Solution.
- Labels:
-
HR Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2018 12:41 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2018 12:41 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2018 09:58 AM
Aman,
Thank you for your reply. The use cases you've described is exactly how it's working. Problem is the requirement is to place the fields on the child tables, not the parent. So what I'm expecting will never happen. I'll create UI Policies on the child tables by HR Service in the meantime. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2018 11:36 AM
I've listed a workaround to add the UI Policy Actions from HR Case child tables below. This prevents the need to have separate UI Policies for each table.
- Open the Hide HR service fields and related lists UI Policy.
- Personalize the list view for the UI Policy Actions related list to display the Table column.
- Locate and open another UI Policy Action that is already configured for the COE child table that you are trying to configure against.
- Select the field you want to create a new action for, change the action behavior (mandatory, visibile, read only), right-click the header and select Insert. This will create a new record associated to the UI Policy with the correct child table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2018 09:13 PM
Great !!
Thank you for Sharing Kiel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2025 11:50 PM
Hi @ARG645 / @Kiel Sanders ,
I understand that this is an old post, but I have a query. If a field created on the parent table was hidden using the UI Policy: Hide HR Service Fields and Related Lists, and later made visible via the Service Table Fields configuration in the HR Service, how can we make it mandatory on load? The field is currently visible across more than 30 HR services, but it needs to be mandatory only for HR cases related to 4 specific HR services. Kindly suggest an appropriate approach.
Regards,
Sujan