What is part of the client-side scripting API?

What is part of the client-side scripting API?

• A. Glide user object (g_user)
• B. GlideRecord
• C. gs
• D. GlideAjax

Answer: (A)

Understanding which objects are available directly in the browser for client-side scripting helps you write UI logic without extra server calls. The Glide user object, accessible as g_user, is part of the client-side scripting API because it exposes information about the currently logged-in user right in the browser. This lets you check user details or roles and tailor the UI without hitting the server, which is exactly what client-side scripting aims to do. In contrast, GlideRecord is a server-side API used to query and manipulate the database from server scripts; gs is the server-side GlideSystem object, also not available in client scripts. GlideAjax, while used from the client to call server-side code, is a mechanism for server communication rather than a client-side data API itself.

Understanding which objects are available directly in the browser for client-side scripting helps you write UI logic without extra server calls. The Glide user object, accessible as g_user, is part of the client-side scripting API because it exposes information about the currently logged-in user right in the browser. This lets you check user details or roles and tailor the UI without hitting the server, which is exactly what client-side scripting aims to do. In contrast, GlideRecord is a server-side API used to query and manipulate the database from server scripts; gs is the server-side GlideSystem object, also not available in client scripts. GlideAjax, while used from the client to call server-side code, is a mechanism for server communication rather than a client-side data API itself.