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

Client-side APIs


The client-side Glide API is partly a subset of the server-side API, but it also provides APIs for dealing with forms and lists. These APIs allow for the control and manipulation of the behavior of elements of the ServiceNow interface, and interaction with the database, user, and session information.

Many client-side APIs don't provide constructor methods, or require instantiation. For example, rather than declaring a new instance of the GlideUser class, we simply have access to the g_user object.

One of the most important things to understand about client-side code is that it can have serious impact on the user experience, in terms of performance. Querying a record from the database, for example, requires constructing a query, sending it across to the server, waiting for the response, and then waiting for all of the data associated with the response to that query (and all of the records contained therein) to be sent back to the client from the server.

While all of this happens...