I am creating a record producer for an HR Service ,should I create in HR Core or HR Portal scope.

[Paul117]

I am creating a record producer for an HR Service ,should I create in HR Core or HR Portal scope.

[Pranav Bhagat · Accepted solution]

From what I can gather, best practice would be to use the HR Service Portal scope for the record producers because they are client facing.According to the documentation also u should create in HR Service Portal scope.

https://docs.servicenow.com/bundle/orlando-hr-service-delivery/page/product/human-resources/task/con...

Regards

Pranav

[Jaspal Singh]

Hi Paul,

All of HR Services are created OOB are in HR Core scope whilst HR Record producers in HR Service Portal.

Even if you mistakenly create it in HR scope you can have it accessed. Only issue at times would be with configuration which you can enable by allowing the Allow Configuration checkbox at the table level for the record.

[Inactive_User57]

i generally keep all my services and rp in the core scope.   it has not ever caused me heartache.

separate scopes also makes it a pain to switch when working on these pieces, with little if any benefit?

what am i missing?

[Christian Prob2]

LOL - GREAT Question!!  I had been chasing the answer to that for a while as well...

Here are my 50 cents:

a) When I took the official HR training, it was strongly recommended to create new (non-Lifecycle) Services from the HR Service Catalogue - using the "New Catalog Item", as that creates automatically the Record Producer (RP), HR Service, and Case Template for you. However, all are created in the same scope.

b) Talking to ServiceNow folks, the recommendation was to create 'normal" HR services in "HR Core" and LifeCycle Event (LCE) ones in "HR Lifecycle Events", nobody ever mentioned 'HR Service Portal'.

c) working with the HR modules for several months, we did not really create anything in the "HR Service Portal" scope and so far we did not have a "$%^&*(*&^%$" moment because of that (fingers crossed and knocking on wood)

d.1) the fact that the regulate ootb ones are in "HR Service Portal" - I never noticed that before - that is kind of a compelling point. None of the matching HR Services is in the "HR: SP" scope, though, surprsingly in a slight contradiction to a) above. And, as @George Floratos  hinted, if you add another scope, you must really really like scope switching pain 😉

d.2) the ootb "Onboarding" one as LCE scenario is in the "HR LC Enterprise" scope, just to make it more diverse 😉

e) RPs also exist and work in UI16 without the Service Portal, so I don't think that RPs 'must' be in a Service Portal scope, not even reading the documentation in any form that this is a recommendation or best practice..

So in summary, I don't thing there is a right or wrong (and more than happy if anyone from  ServiceNow can correct me) - keep it simple and save yourself the scope-switching pain, as that seems to work 😉

Christian