Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning ServiceNow

You're reading from   Learning ServiceNow Get started with ServiceNow administration and development to manage and automate your IT Service Management processes

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher Packt
ISBN-13 9781785883323
Length 358 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
 Hauser Hauser
Author Profile Icon Hauser
Hauser
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Learning ServiceNow
Credits
About the Author
About the Reviewer
www.packtpub.com
Customer Feedback
Preface
1. The Interface FREE CHAPTER 2. Lists and Forms 3. UI Customization 4. Understanding Data and Relationships 5. Tasks and Workflows 6. UI and Data Policies 7. User Administration and Security 8. Introduction to Scripting 9. The Server-side Glide API 10. The Client-side Glide API 11. Server-side Scripting 12. Client-side Scripting 13. Debugging 14. Pro Tips

Chapter 10. The Client-side Glide API

Similarly to the previous chapter, this chapter will focus on the Glide API. Unlike the previous chapter though, this chapter will go over some of the more common client-side Glide API classes, including the following:

  • GlideRecord

  • GlideAjax

  • GlideForm

  • GlideUser

Each class in the Glide API may consist of methods (executable functions within the class), and properties (variables stored within the class, which may be set on initialization of a new instance of the class).

Remember that while the Glide API extends the functionality of client-side scripts, this is done by simply adding certain JavaScript files into the browser's scope. Client-side scripts do not execute on the server, and thus do not execute within Mozilla Rhino. This means that you do not have access to certain Java-ish functionality, but also that you do have access to the browser's scope, certain UI elements and client-side functionality such as DOM (Document Object Model) manipulation, and whatever...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images