From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html g_form.showFieldMsg("field_name", "Hello World", "error"); Puts "Hello World" in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook

In ServiceNow, GlideForm is the client-side API used to interact with and manipulate a record form, including reading and writing field values, controlling visibility/mandatory/read-only behavior, and displaying messages to the user. The platform exposes GlideForm methods through a single global client-side object named g_form. ServiceNow documentation explicitly states that there is no constructor for the GlideForm class and that developers access GlideForm methods using the g_form global object available in client-side contexts such as Client Scripts and UI Policies. This makes g_form the correct and standard way to call GlideForm functions (for example, g_form.getValue(), g_form.setValue(), g_form.setDisplay(), etc.). The other options listed are not the documented GlideForm global object for standard client scripting in ServiceNow.

The correct combination of statements is a, b, and d. These are possible reasons to build custom applications on ServiceNow:
* To replace outdated, inadequate, custom business applications and processes. Building custom applications on ServiceNow can help digitize and automate manual or legacy processes that are not covered by existing ServiceNow solutions. This can improve efficiency, data quality, user experience, and innovation.
* To extend service delivery and management to all enterprise departments. Building custom applications on ServiceNow can help provide consistent and scalable services across different functions and teams in the organization. This can enhance collaboration, visibility, productivity, and customer satisfaction.
* To extend the value of ServiceNow. Building custom applications on ServiceNow can help leverage the capabilities and benefits of the Now Platform, such as low-code development tools, workflow automation engine, AI-powered insights, security operations, etc. This can increase agility, resilience, performance, and value.
The statement c is not a valid reason to build custom applications on ServiceNow:
* To allow users full access to all ServiceNow tables, records, and fields. Building custom applications on ServiceNow does not imply granting users full access to all data and objects in ServiceNow. Access control rules still apply tocustom applications and their components to ensure security and compliance.
Reference: Build Custom Apps in ServiceNow - eBook

Reference:
A module is a navigation item that provides access to a feature or functionality in ServiceNow. Modules must have a link type, which determines how the module behaves when clicked. The following is a list of link types:
Assessment. This is a link type that opens an assessment, which is a survey or questionnaire that measures the effectiveness of a process or service.
List of Records. This is a link type that opens a list of records from a table or a saved filter.
Separator. This is a link type that creates a horizontal line to separate modules in the application menu.
Timeline Page. This is a link type that opens a timeline page, which is a graphical representation of the duration and sequence of events or tasks.
The following are not link types, but other module attributes or field types:
List of Records, Separator, Catalog Type, Roles. These are not link types, but a combination of a link type (List of Records), a module attribute (Separator), a field type (Catalog Type), and a user attribute (Roles).
List of Records, Content Page, Order, URL (from arguments:). These are not link types, but a combination of a link type (List of Records), a module attribute (Content Page), a field name (Order), and a link type argument (URL).
Assessment, List of Records, Content Page, Roles. These are not link types, but a combination of a link type (Assessment), a link type (List of Records), a module attribute (Content Page), and a user attribute (Roles). Reference: Modules, Create a Module