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 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 methods such as addQuery(), which behave...