https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_sc The following are debugging strategies for client-side scripts, which run in the web browser and manipulate the user interface:
* g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.
* Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.
* jslog(). This is a client-side API that writes a message to the browser console.
The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:
* gs.log(). This is a server-side API that writes a message to the system log. References: Client-Side Scripting APIs, Debugging Client Scripts

The elements of an Access Control are evaluated in the following order: Conditions, Roles, Script. The Conditions are a set of criteria that must be met for the Access Control to apply. The Roles are a list of user roles that are required to access the object. The Script is an optional script that can further restrict or allow access based on custom logic. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Reference: Access control rules

The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly('catalog_admin'). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. Reference: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

"Schema map: Provides a graphical representation of the relationships between tables."
https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/table-administration/concept/c_TableAdministration.html

Comprehensive and Detailed Step-by-Step
Inherited fields in ServiceNow are fields that are part of a parent table and automatically become part of child tables through inheritance. This structure is foundational in the ServiceNow data model, ensuring that child tables maintain a consistent relationship with their parent tables.
Here's why inherited fields cannot be deleted from a child table:
System Design:
ServiceNow employs a table inheritance model where child tables derive fields and properties from parent tables. Deleting inherited fields from a child table would break the integrity of the data model, as those fields are shared across multiple tables.
Impact on Functionality:
Many inherited fields, such as sys_created_on or sys_updated_by, are integral to the functionality of the platform. Removing them could disrupt workflows, reporting, and auditing capabilities.
Alternative Approach:
If you want to hide or restrict access to inherited fields in a child table, you can use ACLs (Access Control Lists) to prevent users from viewing or modifying these fields. Another option is to use UI Policies or Client Scripts to control their visibility on forms.
Developer Note:
Attempting to delete inherited fields violates ServiceNow's core principles of maintaining a robust and unified data structure. The platform enforces these rules to ensure consistent behavior across all tables in the hierarchy.
Reference:
ServiceNow Developer Documentation on Table Inheritance.
Best practices outlined on SN Pro Tips regarding scoped application development and table structures.