Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers.
Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form.
Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/client-scripts/ concept/c_CatalogClientScriptCreation.html

In ServiceNow, extending a table means creating a new table (child class) that inherits properties from an existing table (parent class). This inheritance includes fields, business logic, and other configurations, allowing for efficient reuse and customization.
Key Points:
* Field Inheritance: The child table inherits all fields from the parent table. For example, if you extend the Task table, your new table will include fields like "short_description" and "priority."
* Business Logic Inheritance: The child table also inherits business rules, client scripts, and other logic defined on the parent table, ensuring consistent behavior across related tables.
* Access Controls: Access controls are not ignored; instead, the child table inherits the parent table's access controls. However, you can define additional access controls specific to the child table as needed.
* Customization: While the child table inherits many properties, you can add new fields, scripts, and behaviors to tailor it to specific requirements without affecting the parent table.
Reference: For more detailed information, please refer to the official ServiceNow documentation on Table Extension and Classes.

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. References: [ServiceNow Docs - GlideUser API],
[ServiceNow Community - Difference between hasRole() and hasRoleExactly()] Reference: https://community.servicenow.com/community?id=community_question&sys_id=dff705e6db7757c0d58ea345ca96196b

Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. By selecting the Allow access to this table via web services option, you can enable other application scopes to access your data tables using web services, such as SOAP or REST. However, the user performing the query via web services must have the correct permissions to access the table's records.
The user must have the appropriate roles and access controls to perform the operations on the table, such as create, read, write, or delete.
The other statements are not true when this option is selected. This option does not restrict the ability to delete records via web services, nor does it allow records to be always read. The access to the records depends on the user's permissions and the web service method. This option also does not restrict access only to SOAP web services, but applies to both SOAP and REST web services. Finally, this option is not the only way to enable web service access to the table's records. Even when this option is not selected, users with the correct permissions can use web services to access the table's records, as long as they specify the application scope in the web service request.
References:
* Application Access
* Web service access to scoped applications