Book Image

Learning ServiceNow. - Second Edition

5 (1)
Book Image

Learning ServiceNow. - Second Edition

5 (1)

Overview of this book

This book is an updated version of Learning ServiceNow, that will cover the new and updated features of the ServiceNow platform. It will show you how to put important ServiceNow features to work in the real world, while introducing key concepts via examples of managing and automating IT services. It'll help you build a solid foundation of knowledge, and will demonstrate how to effectively implement and configure modules within ServiceNow. We'll show you how to configure and administer your instance, and then move on to building strong user interfaces and creating powerful workflows. We also cover other key elements of ServiceNow, such as notifications, security, reporting, and custom development. You will learn how to improve and automate your business' workflow and processes. By the end of this book, you will be able to successfully configure and manage ServiceNow like a pro.
Table of Contents (19 chapters)
Learning ServiceNow Second Edition


Just like the server-side version, GlideRecord is used to perform database operations on records within ServiceNow, such as querying, modifying, and creating records. The client-side version of the GlideRecord API only contains a subset of the methods available on the server, but it does enable one important new piece of functionality: callback functions.

The query() method of the client-side GlideRecord, as well as insert(), and deleteRecord(), all accept callback functions. In fact, each of these methods should never be called from a client-side script without a callback function.

The full list of documented methods in the client-side GlideRecord API is:

  • addOrderBy()

  • addQuery()

  • deleteRecord()

  • get()

  • getEncodedQuery()

  • getLimit()

  • getTableName()

  • hasNext()

  • insert()

  • next()

  • orderBy()

  • query()

  • setLimit()

In this section, we'll learn about a few of these methods which are commonly used, and which differ from their server-side cousins. This means that we won't be re-hashing...