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.