HR Service configuration

[Kunal36]

Hello All,

Can someone let me know what is the recommendation here - why we should always map a single HR Service to a record producer. Using record producer script, we can derive multiple HR Service to an HR Case but usually while configuring an HR Service, there is a 1:1 mapping to a record producer

[michaelj_sherid]

@Kunal36 The recommended approach is 1-1. If you see the OOtB configurations support this when you create new catalog Items from the Manage HR Catalog module. I feel any other method may cause issues should you want to use conditions (User or HR Criteria ) on the RP or the HR Service.

If my answer has helped with your question, please mark my answer as accepted solutions and give a thumb up.

Regards,

Mike

[abirakundu23]

Hi @Kunal36 ,

Its OOB recommended. One HR service associate to one Record Producer. If you want to use multiple HR services from RP, one service you can consider as a Parent & RP associate with the Parent HR Service & others HR Services can consider as a child services. For case creation for child service, you can use flow designer wrt to Parent HR case.

 It would be a helpful you can follow this approach. 
Using RP script, we can't use multiple HR service for cases creation.

Please mark helpful if it's really worth for you.

[Sandeep Rajput]

@Kunal36 We were in similar situation when we wanted to use multiple record producers for a single HR Service. In order to achieve this, we created a custom field u_hr_service on the Record Producer (sc_cat_item_producer) table and added a related list on HR Service form sn_hr_core_service on the basis of the custom field u_hr_service. 

In the record producer script, instead of using the usual script

new hr_ServicesUtil().createCaseFromProducer(current, producer, cat_item.sys_id);

We are using the following script.

new sn_hr_core.hr_ServicesUtil(current, gs).createCaseFromProducerByService(producer, <sys_id_of_hr_service>, cat_item.sys_id);

Hope this helps.