Service table fields functionality not working?

[alijubran]

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.

[ludijormajordeb]

Hi alijubran,

I have the same question. Did you managed to find the answer for it?

Kind regards,

Ludijor

[alijubran]

Hi ludijormajordebarros,

I found that this functionality was limited to OOB case fields. I didn't explore it much past that and went with Kiel's suggestion to use UI Policies. I was hoping to get around the 'older school' way of setting visibility. Ex If HR Service is XYZ show these fields. Hopefully, there will be some more info on this functionality in later releases. If there is anything I find before that, I'll be sure to post!

Thanks,

Ali

[ludijormajordeb]

Thank you alijubran!!

I was hoping the same, that would definitely help in terms of configuration. I think everyone was expecting that to be the behavior of the OOB functionality.

If I find anything about that I'll also be updating this post.

Kind regards,

Ludijor

[Kiel Sanders · Accepted solution]

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.

[mjepp]

Hi guys,

I thought I would jump in on this since I was working through the same issue in Kingston.   I was able to configure the functionality to work as expected by doing the following.

1:   Created a new Service which created a Case on the "sn_hr_core_operations" table.  

2:   Added a custom field "HRITReason" to the COE table and added it to the form.

3:   Modified the UI policy Kiel listed above, "Hide HR service fields and related lists".   I did an insert and stay on the action as I could not create a new UI action from scratch.

Once I did this my new field displays on the case based on it being configured on the HR Service "Service Table fields".

Regards,

Matt