Pass the ServiceNow Certified Application Developer CAD Questions and answers with Dumpstech

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]

 The application development plan is a document that outlines the scope, objectives, deliverables, and timeline of a software project1. It should include the following business requirements and processes:

Data input/output: This describes what data is needed for the application to function, how the data is collected, stored, processed, and displayed, and what outputs are generated by the application2.

Business problem: This defines the problem or opportunity that the application aims to address, the current situation, the desired outcome, and the benefits of the solution3.

Process steps: This details the steps involved in the application development lifecycle, such as planning, designing, testing, deploying, and maintaining the application4.

Users/stakeholders: This identifies the people who will use, benefit from, or influence the application, their roles, responsibilities, and expectations, and how they will be involved in the project5.

References = 1: Application Development Lifecycle: Phases, Steps and Process3 2: Tips for Writing Business Requirements Documents2 3: Business Requirements Document Template: 7 Components1 4: Requirements Development Steps4 5: What is Business Process Documentation?: 10 Easy Steps to5

Application Files are ServiceNow artifacts comprising an application. An application is a group of files and data that work together to provide a service or functionality. An application file is a specific type of file that belongs to an application, such as a table, a script, a form, a business rule, a UI action, etc. Application files define the structure, logic, and interface of the application. An XML export of an application’s table records, XML exports of an application’s Update Set, and CSV files containing data imported into an application are not examples of application files, as they are data formats that can be used to transfer or store information related to an application, but not the application itself. Reference: Application Files

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

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

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.

"Use an existing MID Server to connect to a Source Control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_SourceControlIntegration.html