CAD Certified Application Developer - ServiceNow Question and Answers

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​.

A possible reason to build a custom app is to fulfill a specific use case on internal processes. For example, you may want to digitize a manual process that is not covered by an existing ServiceNow solution, such as managing inventory, tracking expenses, or scheduling events. Building a custom app on the Now Platform can help you automate workflows, improve data quality, and provide better user experiences. The other options are not valid reasons to build a custom app. To avoid using a code repository like GitHub or GitLab is not a reason to build a custom app, as you can still use source control integration with your custom app development. To create a custom integration for a 3rd party system is not a reason to build a custom app, as you can use integration tools such as IntegrationHub or REST APIs to connect with external systems without creating an app. To replace ServiceNow base tables is not a reason to build a custom app, as it is not recommended to modify or delete base tables that are essential for ServiceNow functionality. Reference: Build Custom Apps in ServiceNow – eBook

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

The server-side API debug log method available for scoped applications is gs.info(). This method logs informational messages that describe the progress of the application. Older methods such as gs.print() and gs.log() are not available in scoped applications. The gs.debuglog() method does not exist. The gs.info(), gs.warn(), gs.error(), and gs.debug() methods work in both scoped applications and global, and are therefore more versatile going forward in future versions. Reference: Debugging best practices

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 Bar Chart and Pie Chart report types can be created by right-clicking on a column header in a table’s list. These report types show how individual pieces of data relate to the whole using proportional bars or slices. You can also choose different aggregation methods such as count, sum, average, min, max, or percent. Reference: [Create reports from lists]

" 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 " .

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. You can use Application Access to control the following database operations:

Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option.

Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option.

Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option.

Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option.

The one database operation that cannot be controlled with Application Access is Query. Query is not an operation, but a method of the GlideRecord class that is used to retrieve records from the database on the server-side. Query is not part of the Application Access rules, but it is affected by the Access Controls and the user’s roles.

ServiceNow tables commonly use table extension, where a child table inherits fields from a parent table. When a field is defined on a parent table, that field is automatically available on all extended child tables. Because of this inheritance model, deleting a field that originates from the parent table effectively removes it from every table that inherits it, which can appear as “the field was removed from multiple tables.” That behavior is characteristic of an inherited field: it is not independently defined on each child table, so it does not exist as separate copies to delete individually. A reference field is simply a field type that points to another table and would not inherently remove itself from multiple tables when deleted. A custom field is typically created on a specific table; deleting it would usually impact only that table (unless that table is a parent and the field is inherited, which is precisely the inherited-field scenario). “Base system field” is not the right explanation for multi-table removal; the key cause is inheritance through table extension.

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

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.”

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

Application developers can specify which ServiceNow page a user sees after submitting a new record using the Record Producer UI by writing a script in the Record Producer’s Script field: producer.redirect = “ < URL > ”;. This script sets the redirect property of the producer object to the URL of the desired page. For example, producer.redirect = “home.do”; will redirect the user to the homepage after submitting the record. The other options are not valid ways to specify the redirect page for a Record Producer. Reference: Populate record producer data and redirect users

The data type of a field determines the format, validation, and display of the field value on a form. When selecting a data type for a field, you should consider the purpose and function of the field. The statements A, C, and D are correct for selecting a data type for a field. For example:

Use the Choice data type to limit options in a field: The Choice data type allows you to create a field that has a predefined set of options for the user to select from. The options can be displayed as a drop-down list, radio buttons, or checkboxes. For example, you can use the Choice data type for a field that indicates the priority of a task.

Use the Phone Number data type to automate phone number data validation: The Phone Number data type allows you to create a field that accepts and validates phone numbers. The field will automatically format the phone number according to the user’s locale and country code. For example, you can use the Phone Number data type for a field that stores the contact number of a user.

Use the string data type for a free-form text field: The string data type allows you to create a field that accepts any text input from the user. The field can have a maximum length of 255 characters. For example, you can use the string data type for a field that captures the short description of an incident.

The statement B is not correct for selecting a data type for a field. There is no Data data type in ServiceNow. To enter the date and time of day, you should use the Date/Time data type. The Date/Time data type allows you to create a field that accepts and displays a date and time value. The field will use a calendar widget and a time picker to help the user enter the value. For example, you can use the Date/Time data type for a field that records the due date of a task.

 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.

Application scope is a foundational concept in ServiceNow application development. ServiceNow documentation describes application scoping as a protection mechanism that identifies and restricts access to an application’s files and data. In practice, scope defines an isolation boundary around an application’s artifacts, such as tables, scripts, UI components, and other resources. This boundary helps prevent unintended interference between applications and reduces the risk of naming collisions or cross-application impacts. The scope model also works together with Application Access settings, which allow administrators to specify what parts of an application are accessible to other applications. By default, scoped applications are designed to keep resources private unless explicitly shared through access settings or cross-scope privileges. Because of this, the primary purpose of scope is not backups or UI design control, and it is explicitly not meant to enable unrestricted updates across applications. Instead, scope exists to define and enforce boundaries so that an application’s resources remain isolated and protected unless intentionally exposed.

It is possible to change an application’s scope in ServiceNow, either from global to private or from private to global. However, changing the scope of an application may affect its functionality and compatibility with other applications. Therefore, it is recommended to test the application thoroughly before and after changing its scope.

How To Change Application Scope In ServiceNow - YouTube

How to move Custom Scoped Applications bettween instances - ServiceNow

Steps to switch a scoped application from your company’s application repository to update sets - ServiceNow

How to change the application (scope) of a SLA Definition without needing to recreate the SLA Definition - ServiceNow

Advantages of Scoped Applications in ServiceNow - QualityClouds

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

To include specific records from a table (often referred to as seed data) when distributing an application in ServiceNow, developers must add these records to the application as application files. This ensures that when the application is installed on another instance, the specified records are included.

Option C is correct because using the " Create Application Files " feature allows developers to select specific records to include in the application package. This process creates application files for the selected records, ensuring they are installed along with the application on other instances.

Options A, B, and D are incorrect:

A: The activation status of Table A and whether it extends the Task table do not determine whether its records are included during installation.

B: Having an automatic number counter and setting a table property do not control the inclusion of records in the application package.

D: The System Clone > Exclude Tables list pertains to cloning operations and does not affect application installation.

For detailed guidance on including table records in application deployments, refer to the official ServiceNow documentation:

SERVICENOW.COM

Client-side scripts run in the user’s browser and are intended to improve or control the form experience. They can hide or show fields, make fields mandatory or read-only, set field values, modify choice list options, and display field or form messages. They should not be used as a true security control because users may bypass client behavior, and they do not directly secure database or backend access. Playbook access and user access are controlled through platform security, roles, ACLs, and application configuration, not ordinary client scripts. In CAD terms, client scripts are primarily for form behavior and user experience. Therefore, B is correct.

In ServiceNow, to create a module that directs users to a Record Producer (a simplified form for creating records), you should use the " URL (from Arguments) " Link Type. This configuration allows you to specify a direct link to the Record Producer.

Steps to Configure:

Navigate to Module Creation:

Go to the Application Menu where you want to add the module.

Click on " Edit Application Menu " and then " New Module. "

Set Link Type:

In the module ' s configuration, set the Link Type to " URL (from Arguments). "

Define the URL:

In the Arguments field, provide the URL to the Record Producer. The URL typically follows this pattern:

arduino

CopyEdit

servicenow_instance_url/com.glideapp.servicecatalog_cat_item_view.do?sysparm_id=record_producer_sys_id

Replace servicenow_instance_url with your instance ' s URL and record_producer_sys_id with the sys_id of the Record Producer.

Explanation of Other Options:

HTML (from Arguments): Used to display custom HTML content. Not suitable for linking directly to Record Producers.

Content Page: Used to display predefined content pages within ServiceNow. Not applicable for direct Record Producer links.

Script (from Arguments): Allows execution of a script to determine the module ' s behavior. This is more complex and unnecessary for simply linking to a Record Producer.

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.

ServiceNow notifications can sometimes be triggered close together for the same record and the same recipients, which can lead to redundant or conflicting messages. To control this, the Notification record includes a Weight field. ServiceNow documentation explains that when multiple notifications are generated for the same target table record and the recipients overlap, the system compares the notifications using the Weight value and sends only the notification with the highest weight. This allows administrators and developers to prioritize the most important notification when multiple are eligible to fire. A common example in the documentation is when an incident is updated (triggering an “commented” notification) and then closed shortly after (triggering a “closed” notification). If both would go to the same user, ServiceNow will select the one with the higher weight, ensuring users receive the most relevant final message instead of multiple emails. This behavior is the intended purpose of Weight: reduce notification noise and prevent conflicts by giving precedence to the highest-weight notification.

Creating an Application Properties page in ServiceNow provides a centralized location where developers or administrators can configure settings that influence the behavior of an application. This approach offers several benefits:

Dynamic Configuration: By exposing certain parameters through an Application Properties page, administrators can adjust the application ' s behavior in response to changing requirements or environments without altering the underlying code or application artifacts.

Simplified Maintenance: Having a dedicated properties page reduces the need for direct modifications to scripts or configurations, thereby minimizing the risk of introducing errors. It also streamlines the process of updating settings, as changes can be made through the user interface.

Enhanced Flexibility: Developers can design applications with configurable options, allowing for greater adaptability across different

 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 to custom applications and their components to ensure security and compliance. Reference: Build Custom Apps in ServiceNow – eBook

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]

Search branch and merge branches are available features in Studio. Search branch allows you to search for a specific branch name or ID in your Git repository. Merge branches allows you to merge changes from one branch to another, resolving any conflicts that may arise. Push to external source control and push to update set are not available features in Studio. Push to external source control is a feature of Source Control Integration, which is a separate application from Studio. Push to update set is a feature of Update Set Previewer, which is also a separate application from Studio. Reference: Studio, Source Control Integration, Update Set Previewer

An application admin is a role that grants full access to an application and its tables, scripts, and other components1. An application admin can create, modify, and delete any element of the application, as well as publish and install it2. An application typically has an application admin role that is automatically created and assigned to the application creator3.

References = 1: Application administration - ServiceNow Docs 2: Application admin role - ServiceNow Docs 3: Application roles - ServiceNow Docs

Debugging client-side scripts in ServiceNow involves utilizing tools and methods that operate within the user ' s browser environment, as client-side scripts execute there.

A. gs.addErrorMessage(): This function is used in server-side scripts to add error messages to the session and is not applicable for client-side debugging.

B. g_form.addInfoMessage(): This client-side function displays informational messages to the user on the form. While primarily used for user communication, it can aid in debugging by confirming the execution of certain script sections.

C. jslog(): This function logs messages to the JavaScript log, which can be viewed using browser developer tools. It ' s a valuable tool for debugging client-side scripts by providing runtime information.

servicenow.com

D. gs.log(): This function logs messages on the server side and is not available in client-side scripting.

Additionally, developers can use the debugger; statement within their client-side scripts. When the browser ' s developer tools are open, encountering this statement will pause script execution, allowing for step-by-step inspection.

Creating applications in ServiceNow can help businesses replace outdated, inadequate, custom business applications and processes, extend service delivery and management to all enterprise departments, and extend the value of ServiceNow by leveraging its platform capabilities and integrations1234.

References = 1: What are Application Services? - ServiceNow 2: What is Application Development? - ServiceNow 3: Custom Applications in ServiceNow - The Cloud People 4: Build Custom Apps in ServiceNow – eBook – ServiceNow

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

Inbound email matching uses Watermarks and Subject lines (with record numbers like INC0010001) to associate emails with existing records.

From Email Handling Docs:

“ServiceNow uses Watermark IDs and subject lines containing record numbers to find the corresponding task or record when processing inbound email.”

 Tables that extend a table inherit the parent’s fields. Extending a table means creating a child table that shares the same columns and business logic as the parent table. For example, the Incident table extends the Task table, which means that all fields defined on the Task table are also available on the Incident table. Extending a table allows for reusing existing fields and behaviors without duplicating them on multiple tables. Reference: Table extension and classes

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.

The steps to import new data into ServiceNow from a spreadsheet are: Load Data, Create Transform Map, Run Transform. Load Data is the process of uploading the spreadsheet file and creating an Import Set table that contains the data to be imported. Create Transform Map is the process of defining how the fields from the Import Set table map to the fields of the target table in ServiceNow. Run Transform is the process of executing the Transform Map and copying the data from the Import Set table to the target table. Reference: Import sets, Transform maps

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

In ServiceNow, UI Actions are elements that facilitate user interaction within the platform, enabling users to perform specific actions such as form submissions, record updates, or triggering workflows. The valid types of UI Actions include:

Form Button: A button displayed on a form that, when clicked, executes a defined action.

Form Context Menu: An option added to the context menu of a form, providing additional actions related to the form ' s record.

Form Link: A hyperlink on a form that directs users to another page or executes a script.

List Banner Button: A button displayed in the banner area of a list, allowing actions to be performed on multiple records simultaneously.

List Choice: An option added to the list context menu for individual records, enabling actions on a selected record.

List Link: A hyperlink in a list that directs users to another page or executes a script.

Record Navigation Button: Buttons that facilitate navigation between records, such as Next and Previous buttons.

Options like " Workflow action " and " Form choice " are not recognized as standard UI Action types in ServiceNow.

For comprehensive details, refer to the official ServiceNow documentation on UI Actions.

When evaluating Access Controls, ServiceNow searches and evaluates:

From the most specific match to the most generic match. This is the correct answer because ServiceNow follows a top-down approach when evaluating Access Control (ACL) rules, which are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. ServiceNow starts with the most specific match, which is the field-level ACL rule, then moves to the table-level ACL rule, and finally to the global or * ACL rule. ServiceNow grants access if any of the ACL rules evaluates to true, and denies access if all of the ACL rules evaluate to false.

The following are not correct descriptions of how ServiceNow searches and evaluates Access Controls:

Only for matches on the current table. This is not correct because ServiceNow does not only look for matches on the current table, but also on the parent tables and the global or * table. For example, if there is no ACL rule for the incident table, ServiceNow will look for an ACL rule for the task table, which is the parent table of the incident table, and then for the global or * table, which is the parent table of all tables.

Only for matches on the current field. This is not correct because ServiceNow does not only look for matches on the current field, but also on the table that contains the field and the global or * table. For example, if there is no ACL rule for the short_description field on the incident table, ServiceNow will look for an ACL rule for the incident table, and then for the global or * table.

From the most generic match to the most specific match. This is not correct because ServiceNow does not follow a bottom-up approach when evaluating Access Controls, but a top-down approach, as explained above. References: Access Control Rules, ACL Evaluation Order

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

Self-invoking. Learn JavaScript!

This type of JavaScript function is known as self-invoking or immediately-invoked function expression (IIFE). It is a function that is defined and executed at the same time, without being assigned to a variable or being called by another function. It is often used to create a local scope for variables and avoid polluting the global namespace. References: [W3Schools - JavaScript Function Definitions], [MDN Web Docs - Immediately-invoked function expressions]

Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only

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

In ServiceNow, to include data from another table within a form, the Reference field type is utilized. A Reference field creates a relationship between the current table and another table by storing a reference to a record in the target table. This allows users to select a record from the referenced table and display related information seamlessly within the form.

A. Use the Date field type: This is incorrect. The Date field type is designed to store date values and does not facilitate referencing records from other tables.

B. Use the Phone Number field type: This is incorrect. The Phone Number field type is intended for storing phone number data and does not support referencing other table records.

C. Use the String field type: This is incorrect. The String field type stores text data and does not inherently provide functionality to reference records from other tables.

D. Use the Reference field type: This is correct. The Reference field type is specifically designed to create a link to a record in another table, enabling the incorporation of related data into the form.

For example, in the Incident table, the " Caller " field is a reference to the User [sys_user] table, allowing the selection of a user as the caller for the incident. This setup ensures data consistency and leverages existing records without data duplication.

For more detailed information, refer to the official ServiceNow documentation on Reference Fields.

Definition of a Spoke:A " spoke " is a scoped application or component of an application that contains Flow Designer actions and integrations. Spokes provide reusable functionality and are typically used to extend the capabilities of Flow Designer.

Why It’s Called a Spoke:

Spokes are part of the ServiceNow Flow Designer framework.

They contain predefined actions that are reusable across multiple flows. For example, an " Email Spoke " might include actions for sending emails or managing email configurations.

Why Other Options Are Incorrect:

Option B (Flow): This refers to an individual flow, not the application containing reusable actions.

Option C (Bundle): There is no such term as " Bundle " specific to Flow Designer in ServiceNow.

Option D (Action): While flows contain actions, the scoped application that houses these actions is referred to as a spoke.

ServiceNow Developer Documentation on Flow Designer Spokes​.

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.

The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.

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]

" 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

https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer

The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform. The Form Designer has four main components:

Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.

Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.

Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.

Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/platform-events/reference/r_ScriptActions.html

User-defined non-inherited fields can be deleted from a table in ServiceNow. These are fields that are created by users on a specific table and are not inherited from a parent table. Inherited fields cannot be deleted from a table, as they are defined on a parent table and shared by all child tables. Any field on a table cannot be deleted, as some fields are system-defined and essential for the table functionality. Table records are not deleted when a field is deleted, as the field deletion only affects the table structure and not the data. Reference: Delete fields

The step that does not belong when creating a Utils Script Include is identifying the table. A Script Include is a server-side script that can contain one or more classes or functions that can be reused by other scripts. It does not depend on a specific table, but can access any table through GlideRecord or other APIs. The other steps are part of creating a Script Include class and its prototype object. References: [ServiceNow Docs - Script Includes], [ServiceNow Docs - GlideRecord API]

ServiceNow supports publishing an application to an application repository, an Update Set, or the ServiceNow Store. These methods allow the application to be installed on other instances or shared with other users.

Publish an application to the application repository

4 Ways to Publish a ServiceNow Application

Publish applications to the ServiceNow Store

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.

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​.

Restricted caller access is enabled through a platform capability delivered as a plugin. The direct method to activate it is to activate the Scoped Application Restricted Caller Access plugin, which turns on the restricted caller access behavior and supporting controls for cross-scope interactions. Additionally, certain ServiceNow applications, such as HR Service Delivery or Security Incident Response, may require this capability and, when requested/installed, can drive activation of the necessary supporting features as part of meeting that application’s security model. That aligns to option B as an activation path tied to obtaining the applications that depend on the feature. Option A is not an activation method, it is a blanket security stance that does not represent how the feature is turned on in the platform. Option D is different functionality: Cross-Scope Access Override is a specific override mechanism for cross-scope calls and does not itself activate restricted caller access. The verified activation methods are the plugin activation and obtaining the applications that require it.

There is no " copy " button on the application record (at least I couldn ' t see one). Also, see here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/reference/r_ManagingApplications.html

" 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