Comprehensive and Detailed In-Depth Explanation:
In ServiceNow, UI Actions are elements that make the user interface more interactive and tailored to user activities. They can appear as buttons, links, or context menu items on forms and lists. The valid types of UI Actions include:
* C. Form choice: These are UI Actions that appear as choices in form context menus, allowing users to perform specific actions related to the form.
* D. Form button: These are buttons that appear on forms, enabling users to execute defined actions directly from the form view.
* E. List banner button: These are buttons that appear in the list view's banner, providing actions that can be performed on the list or selected records.
The other options are not standard UI Action types:
* A. Workflow action: While workflows can include actions, "Workflow action" is not a defined UI Action type in ServiceNow.
* B. Record navigation button: This is not a standard term used for UI Action types in ServiceNow.

gs.print() and gs.log() are older and not available in scoped applications, whereas gs.debug(), gs.info(), gs.
warn(), gs.error() work in both scoped applications and global are therefore are more versatile going forward in future versions.

Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module." The following is true for the Override application menu roles configuration option when configuring a module:
* Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.
The following are not true for the Override application menu roles configuration option when configuring a module:
* Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.
* Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions. Admin is a role

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/useful-scripts/reference
/r_DisplayFieldMessages.html