CAD Certified Application Developer - ServiceNow Question and Answers

 Extending an existing table such as the Task table when creating a new application has several benefits, such as:

You can repurpose existing fields by simply changing the label. For example, you can change the Short description field to Summary or Title for your new table.

You can use existing fields with no modifications. For example, you can use the Assigned to, Priority, and State fields for your new table without changing anything.

Existing logic from the parent table will be automatically applied to the new table. For example, you can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table.

The only option that is not true is d) All of the parent table records are copied to the new table. Extending a table does not copy any records from the parent table to the new table. It only creates a new table that inherits the fields and logic from the parent table.

ServiceNow provides several methods to install applications onto an instance, each suited to different scenarios:

Import an Application from an XML File (Option A):

Description: Developers can export an application as an XML file and then import it into another ServiceNow instance.

Use Case: This method is commonly used for moving applications between instances, such as from development to production.

Procedure:

Navigate to "System Applications" > "Applications."

Click on the "Import" button.

Upload the XML file of the application.

While record producers are powerful tools for creating records via the Service Catalog, they cannot natively redirect users after submission. Redirection typically requires script hacks or custom widget configurations.

From ServiceNow Docs (Catalog Scripting):

“By default, record producers return the user to the catalog homepage. Redirection requires scripting using producer scripts or custom client logic.”

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html

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.

Table Extension in ServiceNow:Extending a table in ServiceNow means creating a child table based on a parent table. The child table inherits the fields, configurations, and functionality of the parent table.

What is Inherited:

Fields: All fields from the parent table are available in the child table.

Functionality: The child table benefits from any business logic or workflows defined for the parent table.

Access Controls: The child table respects the Access Control rules defined for the parent table unless explicitly overridden.

Why Other Options Are Incorrect:

Option B: This is incorrect because the new table does inherit fields from the parent table.

Option C: This is incorrect because you do not need to script or configure behaviors from scratch; they are inherited.

Option D: This is incorrect because Access Controls are not ignored; they still apply and can be extended or modified for the child table.

ServiceNow Developer Documentation on Table Inheritance​.

"If there are no spreadsheets or existing tables to use for your application, you can create and customize a new table." see this quote in link below:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/create-table.html

Also see:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/task/gac-create-table-from-scratch.html

Also, no search results if search on "Now Experience Table Creator".

One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more. References: [Use the REST API Explorer - Product Documentation: Tokyo - ServiceNow], [Introduction to Scripted REST APIs - ServiceNow Developers]

The statements that must evaluate to true for a user to pass an Access Control are:

Conditions configured in the Access Control must evaluate to true.

The user has one of the roles specified in the Required roles related list.

Scripts configured in the Access Control must evaluate to true.

An Access Control is a rule that determines whether a user can access a particular object or operation in ServiceNow. An Access Control consists of three elements: Conditions, Roles, and Script. Each element specifies a requirement that the user must meet to access the object or operation. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Therefore, for a user to pass an Access Control, all three elements must evaluate to true.

The other statements are not required for a user to pass an Access Control. Other matching Access Controls for the records do not need to evaluate to true, as only one matching Access Control needs to return true for access to be granted. The user does not need to be granted access through a business rule, as business rules are not part of Access Controls and do not affect their evaluation. Reference: Access control rules, Access Controls

In ServiceNow, a workflow context refers to a specific instance of a workflow execution. When a workflow is initiated—whether by inserting or updating a record, triggering an event, or through scripts—the system creates a workflow context. This context is derived from a particular version of the workflow and is responsible for executing the defined activities and following the specified transitions within that workflow.

Key points about workflow context:

Instance of Execution: Each time a workflow runs, a new context is created to manage that specific execution instance. This allows multiple instances of the same workflow to operate independently and simultaneously.

Execution of Activities: The context manages the progression through the workflow's activities, ensuring that each step is executed in the defined order and under the specified conditions.

Tracking and Management: Workflow contexts enable administrators to monitor the state and progress of workflow executions. They provide visibility into which activities have been completed, which are pending, and any transitions that have occurred.

For example, if a workflow is designed to handle approval processes, each time an approval is initiated, a new workflow context is created to manage that particular approval instance. This context will track the approval's progress, manage notifications, and handle any branching logic defined in the workflow.

In ServiceNow, Business Rules are server-side scripts that execute whenever a record is inserted, updated, deleted, or queried. However, certain actions can be configured without writing any script, using the Business Rule's user interface options.

The primary actions that can be configured without scripting are:

Set field values: This allows administrators to specify new values for fields when the Business Rule conditions are met. This is configured in the "Actions" tab of the Business Rule form, where specific fields and their desired values can be set without any scripting.

Add message: Administrators can configure a message to be displayed to the user when the Business Rule executes. This is done by selecting the "Add message" checkbox and providing the desired message text.

Options C (Set field values and write to the system log) and D (Set field values and generate an event) would require scripting. Writing to the system log involves using server-side APIs like gs.log(), and generating an event requires calling event generation methods—both necessitate scripting.

For more detailed information, refer to the official ServiceNow documentation on Business Rules:

servicenow.com

Options for Creating Tables in Guided Application Creator:

Create a table from scratch: This option allows you to define a completely new table with custom fields and configurations.

Create a table from a template: You can use predefined table templates to speed up table creation. Templates often include pre-configured fields and settings.

Extend a table: This allows you to create a new table by inheriting fields and functionality from an existing table, enabling reuse and consistency.

Why Other Options Are Incorrect:

Option A (Link to external tables): Linking to external tables is not an option provided in the Guided Application Creator; external data is typically accessed through integration methods.

Option D (Run import jobs): Import jobs are used for data migration, not for table creation in the Guided Application Creator.

Option E (Upload a spreadsheet): While uploading a spreadsheet can create tables, this is a feature of Import Sets, not the Guided Application Creator.

Option F (Use API calls): API calls are for integration and not an option for creating tables directly in the Guided Application Creator.

ServiceNow Developer Documentation on Guided Application Creator​.

The ServiceNow platform is designed to create applications that use forms, workflow, and reporting to solve business problems. Forms are used to interact with data stored in tables, workflow is used to automate and orchestrate processes, and reporting is used to visualize and analyze data. The platform does not require low-level programming libraries or multimedia features, as it provides standard tools and technologies for application development.

References = ServiceNow Certified Application Developer Exam Specification, Application Development Platform – ServiceNow

A transform map determines the relationships between fields in an import set table and fields in an existing ServiceNow table. It also specifies how to transform the imported data before mapping it to the target table.

1. What Exactly is an Import Set? - ServiceNow Developers

Import set table - ServiceNow Application Development [Book]

"By default, all application scope scripts can read the table's records but cannot perform any other database operations." https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/servicenow_administrator/app_store_learnv2_securingapps_tokyo_application_access_database_settings

A Display Business Rule has access to the current, g_scratchpad, and GlideSystem objects, but not the previous object. The previous object is only available to Before Business Rules4. References: Business Rule API

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/business-rules/concept/c_BusinessRules.html

Enabling “Allow access to this table via web services” allows authenticated users with proper roles to access this table via REST/SOAP APIs.

From Development Handbook 4.0.4, p. 191:

"This setting allows web service access to a table, but still requires that users have appropriate roles and permissions through ACLs."

Thus, access isn’t automatic — proper access controls still apply.

Update sets are designed to capture configuration changes while an update set is In progress. Marking an update set Complete is a control point that indicates you are done collecting changes into that set, typically because it is ready to be moved, reviewed, or committed. After completion, the expected and documented practice is to create a new update set for any additional work. This preserves the integrity of the completed set as a stable package of changes and supports clean promotion, troubleshooting, and rollback planning. Deleting the completed update set is not the recommended workflow and can result in losing the historical packaging of captured updates. Modifying a completed update set directly is also not the standard approach because completion is used to prevent accidental addition of further changes and to keep the set consistent for migration. “Reverting to In progress” is not the normal supported lifecycle step for a completed update set in the context of adding more changes. Therefore, the correct approach is to start a new update set and continue development there, keeping the completed set unchanged.

The Guided Application Creator in ServiceNow provides several methods for creating tables within a new application. These options cater to different requirements and data sources:

Extend a Table (Option A):

Description: Create a new table that inherits fields and behaviors from

"There are two possible ways to respond to events:

- Email Notification

- Script Action" - see this quote in link below:

https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/new_to_servicenow/app_store_learnv2_automatingapps_tokyo_responding_to_events

"Application developers must select an application as their current scope context." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

The Guided Application Creator (GAC) is a tool that helps you create applications on the ServiceNow platform by guiding you through the steps of defining the data model, user interface, and logic. When using the GAC, you can designate data tables in three ways:

Upload an existing PDF: You can upload a PDF file that contains the table schema and sample data. The GAC will parse the PDF and create the table and fields based on the file content.

Create a new table on the platform: You can create a new table on the platform by specifying the table name, label, and description. You can also add fields, indexes, and relationships to the table using the GAC.

Upload an existing spreadsheet: You can upload a spreadsheet file that contains the table schema and sample data. The GAC will parse the spreadsheet and create the table and fields based on the file content.

The other options are not valid ways to designate data tables when using the GAC. You cannot upload an existing word processing document or use a freeform database. You can use an existing table on the platform, but you cannot designate it as a data table. You can only use it as a reference table for lookup fields.

The purpose of application scoping is NOT to provide a way of tracking the user who developed an application. Application scoping does not store or display information about the user who created or modified an application or its artifacts. The purpose of application scoping is to provide a relationship between application artifacts, provide a namespace to prevent cross-application name collisions, and provide controls for how scripts from another scope can alter tables in a scoped application. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

Inbound Action scripts are server-side scripts that run when an email is received by the system. They can use the current object to access the record that is created or updated by the email, and the email object to access the properties and methods of the email message. The previous and event objects are not available in Inbound Action scripts. The producer object is only available in Record Producer scripts, which are used to create records from a service catalog item.

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.

ServiceNow Developer Documentation on Table Inheritance​.

Best practices outlined on SN Pro Tips regarding scoped application development and table structures​.

The ServiceNow Store is a marketplace for free and paid certified ServiceNow applications and integrations. The ServiceNow Store provides customers with access to Now Certified enterprise workflow apps from partners that complement and extend ServiceNow products and solutions. Customers can browse, try, buy, and deploy apps and integrations that suit their needs and enhance their ServiceNow experience. The ServiceNow Store is not the source for ServiceNow Community created developer content, as that is available on the Developer Portal or the Share site. The ServiceNow Store is not a downloadable content ServiceNow script archive, as that is available on the Script Library or the Script Repository. The ServiceNow Store is not an alternate name for the ServiceNow Developer Share site, as that is a separate site where developers can share applications, code snippets, UI pages, etc. Reference: ServiceNow Store

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

The method that prints a message on a blue background to the top of the current form by default is g_form.addInfoMessage(). The g_form object is a global object that provides access to form fields and UI elements on a form. The addInfoMessage() method is a method of the g_form object that displays an informational message next to the form header. The message has a blue background color by default, unless it is overridden by a CSS style. The addInfoMessage() method takes one argument, which is the message text to display. References: [ServiceNow Docs - GlideForm (g_form) API], [ServiceNow Docs - g_form.addInfoMessage()]

https://developer.servicenow.com/dev.do#!/reference/api/paris/server_legacy/c_GlideSystemAPI#r_GS-nowNoTZ

The statement that is true for this script fragment is that the method returns true if the currently logged in user has the x_my_app_user role or the admin role. The g_user.hasRole() method is a client-side method that checks whether the current user has a specified role or set of roles. If no role is specified, it returns true if the user has any role. If one or more roles are specified, it returns true if the user has any one of the specified roles. However, this method always returns true if the user has the admin role, regardless of the role parameter. Therefore, in this case, the method returns true if the user has either the x_my_app_user role or the admin role. Reference: User Object Cheat Sheet, Checking user permissions

Web services are software systems that use standardized protocols and formats, such as XML and HTTP, to exchange data and messages between different applications or systems over the Internet or other networks12. Web services enable interoperability and integration among diverse software components, regardless of their programming languages, platforms, or architectures34.

References = 1: What are Web Services? - GeeksforGeeks 2: Web service - Wikipedia 3: What are Web Services? - Online Tutorials Library 4: What is a Web Service? | Webopedia

In ServiceNow, Access Controls (ACLs) determine the permissions required for users to access or modify data. For a user to pass an Access Control, the following conditions must be met:

Conditions configured in the Access Control must evaluate to true: Access Controls can have specific conditions set in the "Condition" field. These conditions are evaluated against the current record, and must return true for the Access Control to grant access.

The user has one of the roles specified in the Required roles related list: Access Controls can specify certain roles that a user must possess to gain access. If the user holds at least one of these roles, this criterion is satisfied.

Scripts configured in the Access Control must evaluate to true: Access Controls can include scripts that perform more granular checks. The script must execute without errors and return true for the user to pass the Access Control.

Option A is incorrect because Business Rules do not grant access; they are server-side scripts that execute based on record operations but do not control security permissions.

Option D is misleading. Each Access Control is evaluated independently. While multiple Access Controls can apply to a single operation, passing one does not inherently grant access unless it is the most specific match.

For more detailed information, refer to the official ServiceNow documentation on Access Controls:

servicenow.com

ServiceNow is optimized for building applications that manage structured data in tables and provide consistent user experiences through lists and forms. A core reason to develop on the platform is when the solution naturally fits the record-based model: users create, review, and update records through forms, and those records drive reporting, auditing, and process automation. That makes option C a direct match to how ServiceNow applications are designed and delivered. Another primary platform strength is workflow automation, including Flow Designer, approvals, task orchestration, notifications, and integration actions that coordinate work across teams and systems. If the solution requires repeatable, governed process automation, option D aligns with the platform’s purpose and capabilities. In contrast, “multimedia features” is not a platform driver for application development; while media can be displayed, it is not the typical reason to choose ServiceNow. Similarly, requiring low-level programming libraries is generally a mismatch, since ServiceNow development focuses on platform APIs and configuration patterns rather than direct access to low-level system libraries.

In ServiceNow, the GlideSystem (gs) object provides several methods for logging messages in server-side scripts. In a privately-scoped application, the following methods are commonly used:

A. gs.log(): This method logs a message to the system log (syslog table). It is a general-purpose logging method that allows developers to record informational messages.

E. gs.info(): This method logs informational messages to the system log. It is functionally similar to gs.log() but is specifically intended for informational messages.

The other options are not standard methods provided by the GlideSystem object:

B. gs.error(): This method does not exist in the GlideSystem API.

C. gs.debug(): This method does not exist in the GlideSystem API.

D. gs.logError(): This method does not exist in the GlideSystem API.

For more detailed information, refer to the official ServiceNow documentation on the GlideSystem API.

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts

The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_IncludeApplicationData.html

In ServiceNow, UI Actions are elements such as buttons, links, and context menu items that allow users to perform actions on records or lists. The three valid UI Action types are:

1. List Banner Button (Option A)

Description: A button that appears in the list view header, allowing users to trigger an action affecting multiple records at once.

Example: A "Bulk Approve" button that processes selected records.

2. Form Button (Option B)

Description: A button that appears on a form, allowing users to trigger actions related to the current record.

Example: A "Submit for Approval" button on an incident form.

3. Record Navigation Button (Option D)

Description: A button that helps users navigate between related records.

Example: A "Go to Parent Record" button that redirects users to a linked record.

Incorrect Options:

Form Choice (Option C):

Not a UI Action type. Choices are typically used in choice fields (dropdowns) rather than UI actions.

List Choice (Option E):

Not a valid UI Action type. Similar to "Form Choice," it pertains to field options rather than UI elements.

Workflow Action (Option F):

Workflows are process automation tools, not UI Actions. They are not directly related to buttons or links that users interact with.

A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.

Application developers configure ServiceNow using industry standard JavaScript to extend and add functionality. JavaScript is a scripting language that enables developers to create dynamic and interactive web pages, as well as manipulate data and logic on the server-side. ServiceNow provides various APIs and frameworks for developers to use JavaScript to customize and enhance the functionality of their applications, such as client scripts, UI policies, business rules, script includes, UI actions, and more. References: [ServiceNow Docs - JavaScript in ServiceNow], [ServiceNow Docs - Scripting in ServiceNow]

In ServiceNow, a Record Producer is a specific type of catalog item that enables users to create task-based records through a simplified interface.

servicenow.com

To create a module that directs users to a Record Producer UI:

Link Type Selection: Choose "URL (from Arguments:)" as the Link Type. This option allows you to specify a direct URL, enabling the module to open the desired Record Producer interface.

URL Configuration: In the "Arguments" field, input the URL that points directly to the Record Producer. This URL typically follows the format:

/record_producer.do?sys_id=

Replace with the actual sys_id of the Record Producer you intend to open.

By configuring the module this way, users accessing it will be presented with the Record Producer's user-friendly interface, facilitating the creation of new records without navigating through the standard form UI.

"You must first select read access to grant any other API record operation." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html

The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:

Can create. This field determines whether users can create records on the application tables.

Can update. This field determines whether users can update records on the application tables.

Can delete. This field determines whether users can delete records on the application tables.

These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.

The following Application Access configuration fields are available regardless of the Can read configuration field:

All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.

Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. References: Application Access, Certified Application Developer (CAD) Learning Path

In ServiceNow, the Application Picker is a tool that allows developers to select the active application scope. When an application is selected from the Application Picker, it sets the Application Scope to that application. This means that any configurations, scripts, or customizations made will be associated with the selected application's scope. Therefore, the correct answer is D.

The other options are incorrect:

A. Selecting Global in the Application Picker sets the Application Scope to Incident: Selecting "Global" sets the scope to the global application, not specifically to Incident.

B. Global is a reserved application which does not appear in the Application Picker: The Global application does appear in the Application Picker and can be selected.

C. Selecting an application from the Application Picker does not set the Application Scope: Selecting an application does set the Application Scope.

For more detailed information, refer to the official ServiceNow documentation on Application Scope.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/form-administration/concept/c_FormDesign.html

The Form Designer is a graphical interface for creating and customizing forms. The following statements are true for the Form Designer:

To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. This will add the field to the form view without changing the table definition.

To create a new field on a form’s table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. This will create a new column on the table and add the field to the form view.

To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. This will remove the field from the form view but not from the table definition.

The following statement is false for the Form Designer:

To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form. This is incorrect because sections are not available in the Field Types tab. To add a section, click the Add Section button on the toolbar or right-click on the form and select Add Section. References: Introduction to App Engine Studio for Developers, ServiceNow Studio Overview, Form Designer

"The sequence is ROLES first, then condition, then script." - Chuck Tomasi says so at this link: https://www.servicenow.com/community/grc-forum/order-of-execution-of-an-acl/m-p/1311962/highlight/true#M6538

Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table]

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.

In ServiceNow, when a new field is added to an existing table, it is not automatically included in any existing List views. List views are predefined configurations that determine which fields are displayed when viewing records in a list format. To display the new field in a List view, you must manually modify the List layout to include the field.

Steps to Add a New Field to a List View:

Navigate to the List Layout Configuration:

Go to the table's list view.

Right-click on the header row (where the column titles are displayed).

Select "Configure" and then "List Layout."

Add the New Field:

In the List Layout configuration, you'll see two columns: "Available" and "Selected."

Locate your new field in the "Available" column.

Use the arrow buttons to move the new field to the "Selected" column, placing it in the desired order.

Save the Configuration:

Click "Save" or "OK" to apply the changes.

The new field will now appear in the List view as configured.

Application Access settings on a table control which operations external applications (in other scopes) can perform. The main controllable operations are:

Can create

Can read (query)

Can update

Can delete

From Development Handbook 4.0.4, p. 192:

“Application access settings determine whether another scope can read, write, create, or delete records from this table... Execute is not a valid database operation — it pertains to script includes or other executable logic.”

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

Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.

The statements A, B, and C are true for Access Controls that have no condition or script. For example:

table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria.

table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria.

table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria.

The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.

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.

When designing forms in ServiceNow, the primary way to organize fields is by using Sections. Sections let developers group related fields into logical blocks, improving readability and guiding users through data entry in a consistent way. In form configuration tools, sections are structural layout elements that define how fields are arranged and presented, allowing developers to separate a form into meaningful areas such as “Requester Details,” “Assignment,” and “Resolution.” This helps reduce clutter on complex forms and supports usability best practices for enterprise applications. A Button is an action control and does not organize fields. A Related list shows records from other tables that are related to the current record; it supports navigation and context, but it does not organize the main record’s fields. Formatters are specialized UI components that can display additional information or UI elements on a form, but they are not the standard feature for grouping and organizing fields in the form layout. Because the question asks specifically about organizing fields during form design, Section is the correct choice.

Create table from template is not an option for creating a table through the Guided Application Creator. The other options are available for creating a table in the app. Upload spreadsheet allows you to import data from an Excel file and create a table based on the spreadsheet columns and rows. Extend a table allows you to create a child table that inherits fields and behaviors from a parent table. Create table from scratch allows you to define your own fields and data types for a new table. Reference: Create tables

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

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideRecordScoped/concept/c_GlideRecordScopedAPI.html

To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.

The following options are not the best ways to see what application artifacts will be in a published application:

Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.

Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.

Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. References: Publish an Application, Application Files

Flow Designer variables can store record data and complex data using the following data types:

Integer: A whole number that can be used in mathematical operations.

Array: A collection of items that can be accessed by their index or iterated over using a For each action.

String: Any kind of text, such as email addresses or the text contents of a file.

Define and Use Data Types in a Flow (Flow Designer)

Variable data types - Power Automate | Microsoft Learn

Product Documentation | ServiceNow

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.

Record Producer Overview:Record Producers in ServiceNow are a way to create records through a simplified user interface. Instead of displaying a typical form, a Record Producer uses a user-friendly UI tailored for quick and intuitive data entry.

Correct Link Type:

The URL (from Arguments) option is used to direct the user to a specific URL, such as the Record Producer interface. You can configure the URL in the module to point to the Record Producer by providing its unique sys_id or name.Example URL:

/catalog.do?sys_id=

Incorrect Options Explained:

Content Page (Option A): This opens a CMS page and is not used for Record Producers.

Script (from Arguments) (Option B): This runs a custom script but does not link directly to a Record Producer.

HTML (from Arguments) (Option D): This is used for rendering custom HTML, not for linking to a Record Producer.

ServiceNow Developer Documentation on Modules and URL Arguments​.