ServiceNow Tips and Tricks

[Mike Allen]

Useful External Websites

These sites are some that I have found in my work as a SN developer.   These are independent of SN, for the most part, but all have useful info and should be included in everyone's toolbelt.

ServiceNow Inc - YouTube

https://styleguide.service-now.com/styles/styleguide/index.html?t=2016-01-07%2011:33:29

http://www.servicenowguru.com/

ServiceNow Developer | ServiceNow tips, tricks and tutorials.

John Andersen-Personal & Professional Website

http://www.snc-blog.com/

http://www.servicenowdiary.com/

GarrettNow | Bite Sized ServiceNow

http://the.servicenowscoop.com/

ServiceNow ELITE.com

Snaug | ServiceNow Advanced Users Group

http://servicenowcms.com/

Service Now Gems

ServiceNow Pro Tips

https://serviceportal.io/

This is by no means comprehensive.   But, apart from the community, this is where I find a large portion of my answers.

CTRL + G

In the script editor, after using CTRL + F to find some string in the code, CTRL + G forwards to the next instance of that search term.  I stumbled upon that and was amazed.

cancel_my_transaction.do

We have all been there.   We run something in production that should take no time and it is, for some reason, not behaving the way it did in sub-prod.   What can you do?   You try to open a new browser window, but you are stuck with this long-running transaction.   In the past, I'd get one of my peers to attempt to lock me out, force the transaction to stop, restart the instance, anything, panicked, just to get it to stop.

Well, here is your answer.   https://instance.service-now.com/cancel_my_transaction.do.     This should be your new first line of defense against runaway transactions.   It won't cancel every time, but it will save your bacon as it has saved mine.

GlideMultipleUpdate

When you absolutely, positively have to change every record in the table, accept no substitutes.

var mu = new GlideMultipleUpdate(table_name);

mu.addQuery('field_name', value);

mu.setValue('field_name',   value);

mu.execute();

This will update all records that follow the query set.   It is very fast, does not touch any system fields (sys_updated_on, sys_updated_by, etc.) and does not run any business rules, so its usefulness is limited to just that.   If you have to update 600k records, and you do not care that the system fields are not updated, use this.