Does "RUN AS" user need to have any roles? or can it be a dummy

[chrischris]

Hey All,

The "RUN AS" field, does anyone know its requirements?

Does the account need to be active? What happens if they aren't active?  

Have roles for the required job? what if they dont have the roles, does it error out or default to a system account(if so which account?)?

Does it depend on the job being "run as" them?

I want to avoid a few issues

1. System admin sets jobs to run as themselves (E.g. Discovery, or reports, entity generators, etc) and leaves, meaning we potentially have to update all of these?
2. The activity formatters which show all the history or the audit logs showing who changes what fields can be very confusing. For example if the job is run as "sally", then suddenly Sally gets messaged asking why she updated XYZ at 3am in the morning. (It wasn't Sally, it was just the system running the job as Sally).
3. AD imports "run as" someone - Then it looks like that person has gone in and updated all the sys_users, when really, the import did....run as that person.  

Ultimately I'd like to run jobs with an empty dummy user account, so they are labelled "correctly". So it an automated job runs to update records or closed out old records, perhaps the user account can be "CleanUpAutomatedAdmin" and so all the tasks show this and we can locate where this script is running etc. As opposed to "sally" where poor sally gets all the blame

Of course if these accounts need roles, roles = Money! So this labeling suddenly becomes a very expensive label... not ideal.

Hope this is clear,

Thanks all

Chris

[vinothkumar]

Hello Saurabh,

Are you sure that Run as user should be active, because we have some scheduled job that was set with inactive users, but still they are running without any issues.

[Saurabh Kumar2]

Not sure in latest release of Service now but earlier there was an issue if user is inactive.

[vinothkumar]

Thanks Saurabh..