PA Job Executions | Run As

[Paula Alejandra]

Hi,

Could anyone help me understand the "RUN AS" field within the PA Job Execution form?

The way I see it, only users with the appropriate role can access Job Executions, hence, I don't understand why they should pick a different "role/person" to run the Job and, which differences could be derived from each choice.

I know there must be a reason for it, but in the training I have only found the "DO THIS" without an explanation about the rational for such an action, and is driving me crazy as I need to understand what I am doing and why am I doing it.

Any help will be really appreciated 🙂

[AndersBGS]

Hi @Paula Alejandra ,

Please see the explanation from the ServiceNow documentation: https://docs.servicenow.com/en-US/bundle/utah-now-intelligence/page/use/performance-analytics/task/t...

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

best regards

Anders

[Paula Alejandra]

Thanks AndersBGS,

So, if I am getting right... as long as there are no separated domains, this RUN AS field shouldn't make any difference. Now, for domain separated instances, the domain from the user selected in the RUN US field will define the data collection... so this means common data [let's take INC for instance] is stored in the same table despite domain separation? This way if Joe [a user with Domain "A"] runs a Job to collect Incident data with his own user, he will get INC data from Domain "A". Now if Joe runs a Job to collect Incident data with Jane's user [being Jane a user with Domain "B"], he will get INC data from domain "B".

Am I getting it right?

[AndersBGS · Accepted solution]

Hi @Paula Alejandra ,

Yes, that is absolutely correct. Please also remember, that a PA job need to be run by an active user. If the user becomes inactive, the jobs will not run.

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

best regards

Anders