Which is part of the client side scripting API?

Which is part of the client side scripting API?

• A. glide user object(g_user)
• B. GlideRecord
• C. GlideSystem
• D. gs_info

Answer: (A)

Client-side scripting runs in the browser and uses APIs that are available in the client context. The GlideUser object, exposed as the global g_user, is part of this client-side API. It lets you access information about the currently logged-in user and perform lightweight checks (like whether the user has a certain role) without needing a server call. This kind of information is typically used to tailor UI behavior or form logic directly on the client. In contrast, GlideRecord, GlideSystem, and gs_info are server-side APIs. They run on the server and are used in server-side scripts such as Business Rules, Script Includes, and other server contexts. They cannot be invoked from client-side scripts the way g_user can. So the Glide User object (g_user) is the one that belongs to the client-side scripting API.

Client-side scripting runs in the browser and uses APIs that are available in the client context. The GlideUser object, exposed as the global g_user, is part of this client-side API. It lets you access information about the currently logged-in user and perform lightweight checks (like whether the user has a certain role) without needing a server call. This kind of information is typically used to tailor UI behavior or form logic directly on the client.

In contrast, GlideRecord, GlideSystem, and gs_info are server-side APIs. They run on the server and are used in server-side scripts such as Business Rules, Script Includes, and other server contexts. They cannot be invoked from client-side scripts the way g_user can.

So the Glide User object (g_user) is the one that belongs to the client-side scripting API.