Exam CAD topic 1 question 24 discussion

https://developer.servicenow.com/dev.do#!/reference/api/vancouver/client/c_GlideUserAPI C

UI actions is a server side artifact but it can also run on client. hence g_user can be used on any client side scripts

- is typically used in client scripts and UI policies but is also found in UI actions that run on the client. - cannot be used in business rules or UI actions that run on the server. Source: https://developer.servicenow.com/dev.do#!/reference/api/utah/client/c_GlideUserAPI

g_user can be used on Client Side Scripts: 1. Client Script 2. UI Policy Script 3. UI Action (if client checkbox is true)

The correct answer is C, although GlideUser is not COMMONLY used in UI Actions, you can make a UI Action run client side. Running a UI action client side is also how you integrate GlideModal and other client operations with a UI Action. Tricky question, but the answer is C.

Search in the doc UTAH version: "is typically used in client scripts and UI policies but is also found in UI actions that run on the client." So, the correct answer is C.

The link being shared says that the GlideUser API cannot be used in UI actions that run on the server. This question doesn't specify if the UI Action runs on the client or on the server. For that reason, I believe the correct answer is A. The GlideUser is typically used in client scripts and UI policies. Unless it is specified where the UI Action is running I will not assume is on the client side. A very tricky question indeed.

"CAN" is a key word interpretation that needs to be understood for this question. "Can be used in Client Scripts, UI Policies, and UI Actions" as is mentioned below. Read these details carefully. https://developer.servicenow.com/dev.do#!/reference/api/tokyo/client/c_GlideUserAPI

A is correct

C is correct - Can be used in Client Scripts, UI Policies, and UI Actions. https://developer.servicenow.com/dev.do#!/reference/api/tokyo/client/c_GlideUserAPI

answer is client scripts and ui policies only, Please correct the answer in website

GlideUser The GlideUser API provides access to information about the current user and current user roles. Using the GlideUser API avoids the need to use the slower GlideRecord queries to get user information. The GlideUser methods and properties are accessed through a global object (g_user) that is only available in client scripts. GlideUser contains name and role information about the current user. is typically used in client scripts and UI policies but is also found in UI actions that run on the client. cannot be used in business rules or UI actions that run on the server. (Refer:https://developer.servicenow.com/dev.do#!/reference/api/tokyo/client/c_GlideUserAPI)

UI action works as both client and server side So Answer C is correct

A https://servicenowguru.com/scripting/user-object-cheat-sheet/#:~:text=The%20g_user%20object%20can%20be,accessible%20to%20client%2Dside%20JavaScript.