Which statement about client-side scripting in ServiceNow is true?

Which statement about client-side scripting in ServiceNow is true?

• A. Client-side scripts have access to Glide User (g_user) methods
• B. Client-side scripts can call any server-side function directly
• C. Client-side scripts can modify database records without server calls
• D. Client-side scripts do not run in the user's browser

Answer: (A)

In ServiceNow, client-side scripting runs in the user's browser and can access the g_user object, which provides information about the current user and exposes methods you can use to check roles and other attributes. This lets client scripts tailor behavior without hitting the server. So the statement that client-side scripts have access to g_user methods is true, because g_user is designed for use in client scripts to probe user permissions and context. It's important to distinguish this from server-side access. Client-side code cannot call server-side functions directly; to perform server operations you must use mechanisms like GlideAjax or server-side scripts that run on the server. Similarly, modifying database records is a server-side action and requires a server call. Finally, client-side scripts do run in the user's browser, so asserting that they do not run in the browser would be incorrect. Understanding this helps you write client scripts that respond to user context efficiently while knowing when server interactions are required for data changes.

In ServiceNow, client-side scripting runs in the user's browser and can access the g_user object, which provides information about the current user and exposes methods you can use to check roles and other attributes. This lets client scripts tailor behavior without hitting the server. So the statement that client-side scripts have access to g_user methods is true, because g_user is designed for use in client scripts to probe user permissions and context.

It's important to distinguish this from server-side access. Client-side code cannot call server-side functions directly; to perform server operations you must use mechanisms like GlideAjax or server-side scripts that run on the server. Similarly, modifying database records is a server-side action and requires a server call. Finally, client-side scripts do run in the user's browser, so asserting that they do not run in the browser would be incorrect.

Understanding this helps you write client scripts that respond to user context efficiently while knowing when server interactions are required for data changes.