Book Image

Mastering ServiceNow Scripting

By : Andrew Kindred
Book Image

Mastering ServiceNow Scripting

By: Andrew Kindred

Overview of this book

Industry giants like RedHat and NetApp have adopted ServiceNow for their operational needs, and it is evolving as the number one platform choice for IT Service management. ServiceNow provides their clients with an add-on when it comes to baseline instances, where scripting can be used to customize and improve the performance of instances. It also provides inbuilt JavaScript API for scripting and improving your JavaScript instance. This book will initially cover the basics of ServiceNow scripting and the appropriate time to script in a ServiceNow environment. Then, we dig deeper into client-side and server-side scripting using JavaScipt API. We will also cover advance concepts like on-demand functions, script actions, and best practices. Mastering ServiceNow Scripting acts as an end-to-end guide for writing, testing, and debugging scripts of ServiceNow. We cover update sets for moving customizations between ServiceNow instances, jelly scripts for making custom pages, and best practices for all types of script in ServiceNow. By the end of this book, you will have hands-on experience in scripting ServiceNow using inbuilt JavaScript API.
Table of Contents (18 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Debugging tools best practices


As we have discovered in previous chapters, there are many ways to debug in ServiceNow. Each developer will have their own favorite methods, and also, there are better ways to debug different scenarios.

Logging

One of my favorite ways of debugging is using logging techniques such as gs.log. In earlier chapters, we saw that these logs can be added to a script, and when the script runs, we see these logs in the system log for the ServiceNow instance. 

However, we must ensure that this debugging is never seen in a production instance. It is a good practice to check each script that you write to ensure that no debugging is left in the final version. It can be a good idea to check the system log before your newly created script is executed and then again once you have finished. If there are any logging messages that are sent, then these should be removed before the new functionality is sent to a production instance.

It is also important to make sure that you make your...