Service table fields functionality not working?

alijubran · ‎10-10-2017

Is there somewhere other than the HR Service record that we indicate a field is to be used as a'Service table fields'? If I create a custom field that is needed for a service, I have added it to the Service table fields slushbucket but that field still shows up for all HR Services.

I am assuming I have to indicate somewhere that the fcustom field is a field that should hide/show based on HR Service.

Kiel Sanders · ‎01-15-2018

Hi Ali and Ludijor

Sorry, I misunderstood Ali's initial question. The HR Service Table Fields do react in the behavior you are both expecting. They are designed for a user to designate the fields applicable to the HR Service during configuration. When the HR Service field changes on a case, the "Show HR service fields" client script is triggered to show/hide the fields based on the new HR Service.

The problem you may both be encountering is that the client script only runs on field change and therefore the new field will display until another HR Service is selected and triggers the field to be hidden. There is an additional piece of configuration necessary for these situations with custom fields. The "Hide HR service fields and related lists" UI Policy is used to indicate what fields should be hidden on page load so you'll want to configure your new custom field to be not visible here.

Also, there is a known issue right now with not being able to select fields from a COE table since the UI Policy is set to HR Case. A temporary workaround is to switch the UI Policy to the COE table, save, add your COE specific fields to the UI Policy Actions, and then switch the UI Policy back to HR Case. We are exploring alternate solutions for this in future releases.

We realize this information is not well documented so I'll work with the team to ensure it is gets added to the product documentation.

View solution in original post

alijubran · ‎01-15-2018

Matt, you are the MAN!!! Thanks for putting these steps up here.

alijubran · ‎01-15-2018

Looks like this is it. The UI Policy was the missing ingredient.

Bascially, UI Policy hides -- Client Script shows based on HR Service

ludijormajordeb · ‎01-15-2018

Thank you very much guys kielsanders alijubran mjepp

G24 · ‎11-14-2023

Hello @Kiel Sanders . Are you still with ServiceNow? Is there now some documentation on this feature? Where, please?

In my custom "HR Service" on the "HR Service Additional Information" tab, for field "Service table fields" I added ALL of the available fields (over 100 I believe), and only about 10 of them seemed to actually SHOW UP on a newly instantiated HR Case record. See here:

michaelj_sherid · ‎11-14-2023

@G24 the functionality has changed a bit since 2018 when this post originated. If you have added your fields to the UI policy and they are not showing after configuring them in the HR Service, you may have scope issues. Are the fields created in the same scope as the table? In the newer functionality of Service Table fields, this can make a difference.

Regards,

Mike