ServiceNow Updated CAD Exam Questions and Answers by chase

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/guided-app-creator.html

The following is true for GlideUser (g_user) methods:

Can be used in Client Scripts, UI Policies, and UI Actions. This is true because GlideUser (g_user) methods are part of the client-side scripting APIs that provide information about the current user and the user’s preferences. Client Scripts, UI Policies, and UI Actions are all types of client-side scripts that run in the web browser and manipulate the user interface.

The following are not true for GlideUser (g_user) methods:

Can be used in Client Scripts and UI Policies only. This is false because GlideUser (g_user) methods can also be used in UI Actions, which are another type of client-side scripts that can be triggered by a user’s click on a button, link, or choice.

Can be used in Business Rules only. This is false because GlideUser (g_user) methods cannot be used in Business Rules, which are server-side scripts that run on the ServiceNow platform and manipulate the database. Business Rules use a different API to access the current user information, which is GlideSystem (gs).

Can be used in Business Rules, and Scripts Includes. This is false because GlideUser (g_user) methods cannot be used in Business Rules or Script Includes, which are both server-side scripts. Script Includes are reusable units of code that can be called from any server-side script. Script Includes also use GlideSystem (gs) to access the current user information. References: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes

Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:

gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole(‘admin’) will return true if the user is an administrator, and false otherwise.

current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.

The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.

References:

[Access Control scripts]

[GlideSystem methods]

[GlideRecord methods]

In ServiceNow, when a table is extended from a parent table, it inherits all fields from the parent. These inherited fields are integral to the structure of the child table and maintain the relationship between the parent and child tables. As a result, inherited fields cannot be deleted from the child table.

Key Points:

Inheritance Structure: The child table's structure is designed to include all fields from the parent table to preserve data integrity and ensure consistent behavior across the hierarchy.

System Constraints: ServiceNow does not provide an option to remove inherited fields from the child table. Attempting to delete such fields would disrupt the inheritance model and potentially cause system inconsistencies.

Alternative Approaches: While you cannot delete inherited fields, you can manage their visibility:

Form Layout: Adjust the form layout to hide inherited fields that are not relevant to users interacting with the child table.

Access Controls: Implement access controls to restrict visibility or edit permissions for specific fields based on user roles.