Book Image

ServiceNow: Building Powerful Workflows

By : Tim Woodruff, Martin Wood, Ashish Rudra Srivastava
Book Image

ServiceNow: Building Powerful Workflows

By: Tim Woodruff, Martin Wood, Ashish Rudra Srivastava

Overview of this book

ServiceNow is a SaaS application that provides workflow form-based applications. It is an ideal platform for creating enterprise-level applications, giving requesters and fulfillers improved visibility and access to a process. ServiceNow-based applications often replace email by providing a better way to get work done. This course will show you how to put important ServiceNow features to work in the real world. We will introduce key concepts and examples on managing and automating IT services, and help you build a solid foundation towards this new approach. You will then learn more about the power of tasks, events, and notifications. We’ll then focus on using web services and other mechanisms to integrate ServiceNow with other systems. Further on, you’ll learn how to secure applications and data, and understand how ServiceNow performs logging and error reporting. At the end of this course, you will acquire immediately applicable skills to rectify everyday problems encountered on the ServiceNow platform. The course provides you with highly practical content explaining ServiceNow from the following Packt books: 1. Learning ServiceNow 2. ServiceNow Cookbook 3. Mastering ServiceNow, Second Edition
Table of Contents (39 chapters)
Title Page
Credits
Preface
Free Chapter
1
Module 1
36
Bibliography

Logging


Note

Note: While there is a feature called Session debug logging, this section is about the system log and how to use logging within scripts effectively for troubleshooting your code.

Logging is something that you can employ both server-side, and client-side. There are several useful logging API methods that can be employed for various purposes, and in different situations: info(), warn(), and error(), each with respectively higher levels of significance. These three types of logging methods are available both from the GlideSystem API (available within all server-side scripts as the gs object) on the server, and from the console API on the client.

An informational message (using gs.info() on the server, or console.info() on the client) is meant to inform a curious admin perusing the logs, of some important state information, or perhaps about successful execution and final state of a particularly complex script. This is especially useful when no other state information is necessarily...