Experience on HR service in HRSD module.

[Meloper]

Hi all,
I would like to use this forum to get personal experiences and opinions from you guys, no docs links or anything else 🙂

1. what do you think is the importance of HR Service?
- I would say it is the core and the main component of the HRSD module or?

2. what exactly is the function or benefit of the COE field? Can you give examples or use cases.

3. why is it possible to assign a different table to the HR Service or this COE field, than maybe an assigned Record Producer, records creates? so e.g. the Servicee (COE) can be assigned to the HR Payroll Case table, but the Record Producer creates a record in the HR Benefits Case table.

4. if you add a FLow to a HR Service (via the field), the only advantage is that you can recognize it better as an agent or admin, right? I mean the condition for the flow is built directly in the FLow.
I can also assign another FLow to a service, the flow is not triggered by the service?

5. also a record producer is only connected to the service for the overview. That a Hr Case has the service in the FIELD "hr service", happens through a script in the RP and not ALONE through the fact that the RP is assigned to the service?

6. does it make sense to assign multiple Record Producer to a single service?

7. the HR ServiceField on a HR Case is always a mandatory field.
Would you say that the use of a Service should be 1 to 1 with a Record Producer?

I would be mega happy about suggestions and experiences. Even if it is not to all points.
Best regards