CAD Certified Application Developer - ServiceNow Questions and Answers

ServiceNow provides several methods for developers to publish and share applications once they are ready for distribution. The supported methods include:

Publish to an application repository: This method allows developers to publish their applications to a centralized repository, enabling easy distribution and installation across multiple ServiceNow instances. The application repository serves as a hub where applications can be stored and accessed by other instances.

snowunderground.com

Publish to the ServiceNow Store: Developers can submit their applications to the ServiceNow Store, a marketplace where applications are reviewed, certified, and made available to all ServiceNow customers. Publishing to the Store involves a certification process to ensure the application meets ServiceNow ' s standards.

support.servicenow.com

Publish to an update set: An update set is a container for capturing configuration changes in ServiceNow. Developers can publish applications to an update set, which can then be moved between instances, allowing for the transfer of application configurations and customizations.

servicenow.com

Options A (Publish to a spreadsheet), D (Publish to a local USB device), and F (Publish to a local drive) are not supported methods for publishing applications in ServiceNow. These options do not align with the platform ' s mechanisms for application distribution and deployment.

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

Delegated Development is intended to let administrators grant controlled development permissions to non-admin developers for a specific scoped application . Within that model, admins can allow delegated developers to work on application artifacts and administration tasks that are still limited to the application scope. One of the permitted areas is managing security artifacts , which includes creating and maintaining Access Controls (ACLs) and related security configuration for the application’s tables and resources. That aligns directly to option C . Administrators can also grant the permission to delete the scoped application, which aligns to option D and is treated as a high-impact capability that is explicitly controlled by delegated development permissions. By contrast, option A is not valid because delegated development is for scoped applications and does not grant authority to develop or deploy global applications. Option B is not a delegated development permission category; coalesce configuration is part of import/set-up behavior and is not represented as a delegated developer permission in the application development permission set.

The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

Flow Designer runs automation based on triggers . A primary trigger type is a Record trigger , which starts a flow when a record is created, updated, or created or updated . This matches option A and is one of the most common ways to automate application behavior using table data. Flow Designer also supports triggers tied to SLA-related events , enabling flows to react when an SLA is approaching breach or breaches, which aligns to option E in the way the platform exposes SLA timing events for automation. In addition, flows can be started by an inbound request through supported APIs, allowing external systems or scripts to invoke flow execution, which aligns to option F. By contrast, elevating to security_admin is a privileged security operation, not a Flow trigger; logging in as a specific user is an authentication/session activity rather than an automation trigger; and outbound email is typically an action that a flow can send, not an event that triggers a flow. The correct answers focus on documented Flow trigger categories rather than UI or security behaviors.

In ServiceNow, when developing within a privately-scoped application, certain logging methods are recommended for use in server-side scripts to ensure proper logging and debugging. The GlideSystem (gs) object provides several methods for this purpose:

gs.debug():

Description: Logs messages at the " Debug " level.

Usage: gs.debug( ' Debug message here ' );

Purpose: Useful for logging detailed information during development and troubleshooting. These messages are typically only visible when the system ' s logging level is set to " Debug. "

gs.error():

Description: Logs messages at the " Error " level.

Usage: gs.error( ' Error message here ' );

Purpose: Used to log error messages that indicate a problem that might still allow the application to continue running.

gs.warn():

Description: Logs messages at the " Warning " level.

Usage: gs.warn( ' Warning message here ' );

Purpose: Used to log potentially harmful situations that are not necessarily errors but may require attention.

gs.info():

Description: Logs messages at the " Information " level.

Usage: gs.info( ' Information message here ' );

Purpose: Used to log informational messages that highlight the progress of the application at a coarse-grained level.

Deprecated or Unsupported Methods in Scoped Applications:

gs.log():

Description: This method is not supported in scoped applications. It is restricted to the global scope and is not accessible from a private scope. Therefore, it should be avoided in privately-scoped applications.

" Guided Application Creator is enabled via the Guided Application Creator (com.glide.sn-guided-app-creator) plugin, which is active by default in the Now Platform. " Located under " Activation Information " section at this URL:

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

The Automated Test Framework (ATF) is a tool that allows you to create and run automated tests on the ServiceNow platform. The ATF uses test steps to define the actions and validations for each test. The test step that allows you to create a user with specified roles and groups for the test is the Create a user test step. This test step creates a temporary user record that is deleted at the end of the test. You can specify the user name, password, roles, and groups for the user. You can also use the Impersonate a user test step to switch to the created user and perform actions as that user.

The other options are not valid test steps for creating a user. The Create a role and Create a group test steps do not exist in the ATF. To create a role or a group, you need to use the Create a record test step and specify the sys_user_role or sys_user_group table. The Impersonation test step does not create a user, but switches to an existing user.

Application Access on a table defines cross-scope behavior at the table boundary. To ensure that no other application scope can create records on the application’s data tables, the table must be restricted so that only the owning scope can access it. Setting Accessible from to This application scope only enforces that boundary by preventing other scoped applications from accessing the table, including record creation. This is exactly what the requirement describes: blocking other private scopes from creating records on the table. The “All application scopes” option is the opposite of what you want because it opens cross-scope access, and then trying to selectively block “Can create” still leaves broader exposure and is not aligned with the stated goal. Creating ACLs to block other scopes is also not the correct approach for cross-scope isolation because ACLs primarily control user and role access, while cross-scope access is governed by Application Access and cross-scope rules. Disabling “Allow access to this table via web services” is about API/web service exposure, not about other application scopes creating records through normal platform access.

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

An example of when an application might not use a Scheduled Script Execution (Scheduled Job) is when the application needs to run a client-side script at the same time every day. A Scheduled Script Execution is a server-side script that runs on a specified schedule and performs some action on the server or database. A client-side script runs on the user’s browser and cannot be scheduled by ServiceNow. The other options are examples of when an application might use a Scheduled Script Execution, such as sending email reminders, running a clean up script, or querying the database for unassigned records. Reference: Scheduled Script Execution, Client scripts

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.

" Restricted caller access [sys_restricted_caller_access] records track cross-scope applications or scripts that request access to an application, application resource, or event in the Now Platform. " < < == this is the third sentence down in the following link: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/restricted-caller-access-privilege.html

 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

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_flowdesigner_tokyo_flow_designer/app_store_learnv2_flowdesigner_tokyo_notifications_in_flow_designer/app_store_learnv2_flowdesigner_tokyo_inbound_email_and_flows

" By default, the system generates a watermark label at the bottom of each notification email to allow matching incoming email to existing records. " https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/concept/c_WorkingWithWatermarks.html

Recurring checks, like finding task records that are unassigned, are implemented using platform automation that runs on a schedule . ServiceNow provides two common development-aligned places for this type of logic. Scheduled Script Execution is a scheduled job mechanism that runs server-side scripts at defined intervals. Developers use it to query tables (such as Task) and take actions like updating fields, creating follow-up records, or sending notifications when conditions are met. This matches option C . For low-code automation, Flow Designer also supports scheduled triggers , allowing developers to run a flow at specific times or on a repeating schedule to perform checks and actions. This matches option A (Scheduled Flows). Discovery Schedules are specific to the Discovery feature set for scanning infrastructure and are not used for general task management checks. “System Schedules” is not the standard construct where custom recurring business logic is authored for application development; the platform’s scheduled logic is typically implemented through scheduled jobs (including script executions) and scheduled flow triggers.

Application Properties let developers expose configurable values (via system properties), so behavior can be changed without altering code .

From Development Handbook 4.0.4 , p. 167:

“Use application properties to enable or disable features or change behavior without modifying scripts directly . This promotes modularity and flexibility.”

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

 It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan. The following are some of the considerations to document as part of the business process:

Business problem. This is the description of the problem or opportunity that the application is intended to address or exploit. It should include the background, context, scope, and objectives of the problem or opportunity.

Data input/output. This is the specification of the data that the application will need to collect, store, manipulate, and display. It should include the data sources, formats, validations, transformations, and integrations of the data.

Users/stakeholders. This is the identification of the users and stakeholders who will be involved in or affected by the application. It should include the roles, responsibilities, expectations, and needs of the users and stakeholders.

Process steps. This is the definition of the steps and activities that the application will perform or support. It should include the inputs, outputs, triggers, conditions, and outcomes of each step or activity.

The following are not some of the considerations to document as part of the business process:

Project schedule. This is the estimation of the time and resources required to complete the application development project. It should include the milestones, deliverables, dependencies, and risks of the project. This is not part of the business process, but part of the project management plan.

Database capacity. This is the measurement of the amount of data that the application will generate and store in the database. It should include the data volume, growth rate, retention policy, and backup strategy of the data. This is not part of the business process, but part of the technical design and architecture of the application.

Available licenses. This is the number and type of licenses that the application will consume or require from the ServiceNow platform. It should include the license model, cost, and allocation of the licenses. This is not part of the business process, but part of the financial and legal aspects of the application. References: Application Development Process, Business Process Analysis

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

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

The Weight field in an Email Notification determines which notification is sent when multiple notifications are triggered for the same record and recipients. Only the notification with the highest weight is sent. A weight value of zero means the notification is always sent when the notification’s When to send criteria is met. A weight value of -1 means that no email should be sent3. References: Email Notification Weight

To allow a module to open a form for new record insertion, the Link type should be set to “Create new record” or similar.

From Platform App Design Docs :

“Modules control navigation behavior via the Link type setting. To insert records, use the ' Create record ' or ' New record ' link type.”

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

" 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

The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. The following is true for a table with the Allow configuration option selected:

Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.

The following are not true for a table with the Allow configuration option selected:

Only the in scope application’s scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.

Any user with the application’s user role can modify the application’s scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application’s user role. To modify the application scripts, users need to have the admin role or the application’s admin role.

Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application’s admin role and be in the application scope. References: Application Access, Business Rules

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/set-RCA-level.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

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.

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.

When a ServiceNow instance requests information from a web service, ServiceNow is the web service consumer. A web service consumer is an application that sends requests to a web service provider and receives responses from it. A web service provider is an application that exposes its functionality as web services. A web service publisher is a person or organization that publishes web services for others to use. A web service specialist is a person who has expertise in developing or using web services. Reference: Web services

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

Update Sets group configuration changes for deployment across environments (e.g., from dev to test). They don’t track data or metrics.

From Development Handbook 4.0.4 , p. 213:

“Update Sets are used to track and bundle changes , allowing developers to promote and test configuration updates between instances.”

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.

In ServiceNow, a Record Producer allows users to create records in a specific table through the Service Catalog. After a user submits a Record Producer, developers may want to redirect the user to a specific page. This can be achieved by setting the producer.redirect property within the Script field of the Record Producer.

For example:

javascript

CopyEdit

producer.redirect = ' incident.do?sys_id= ' + current.sys_id;

This script redirects the user to the newly created incident record after submission.

Option A is incorrect because configuring the module that opens the Record Producer does not control the post-submission behavior.

Option C is unnecessary for simple redirection purposes; creating an application property to store the URL adds unnecessary complexity.

Option D is incorrect because using window.redirect in a Business Rule is not appropriate; Business Rules run on the server side and do not have access to the client-side

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]

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

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.

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

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. By setting the Accessible from field value to This application scope only, you can restrict the access to your data tables to only your application scope. This means that other application scopes cannot create, read, write, or delete records on your data tables, unless they have explicit permissions through Access Controls or other means.

In ServiceNow, Application Files are configuration records that define the various components and logic that constitute an application. These include artifacts such as:

Business Rules

Client Scripts

UI Actions

Script Includes

Tables and Fields

Workflows

These artifacts collectively define the functionality and behavior of the application. When an application is developed, ServiceNow automatically creates and manages these Application Files to represent the application ' s components.

Option C is correct because Application Files are the fundamental building blocks that comprise a ServiceNow application, representing its various components and configurations.

Options A, B, and D are incorrect:

A: XML exports of an Update Set represent changes made to an instance but are not synonymous with Application Files.

B: CSV files are typically used for data import/export and do not represent the configuration components of an application.

D: An XML export of table records pertains to data within a table, not the configuration artifacts that define application behavior.

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.

Flow Designer is a no-code platform capability that lets you automate business processes in a single drag-and-drop design environment. Some of the features of Flow Designer are:

Add stages to a flow: You can define the stages of a flow to track its progress and status. Stages can be used to group actions, subflows, and conditions into logical units.

Call a flow from another flow or subflow: You can reuse existing flows or subflows by calling them from another flow or subflow. This allows you to modularize your automation and avoid duplication of logic.

Test a flow using the “Run as” feature: You can test a flow using the “Run as” feature to specify the user context and input parameters for the flow execution. This helps you to verify the functionality and performance of your flow before publishing it.

Flow Designer – No-Code Workflows - ServiceNow

Flow Designer - ServiceNow

Flow Designer Data Sheet - ServiceNow

In ServiceNow, when an event is generated using the gs.eventQueue() method, the system can respond in several ways:

B. Email Notification: Events can trigger email notifications. By associating an event with a notification, the system can send emails to specified recipients when the event occurs.

E. Script Action: Script Actions are server-side scripts that execute in response to events. They allow developers to define custom behaviors that should occur when specific events are fired.

The other options are not appropriate responses to events generated by gs.eventQueue():

A. UI Policy: UI Policies are used to dynamically change the behavior of fields on forms in the user interface and are not triggered by events.

C. Client Script: Client Scripts run on the client side (in the user ' s browser) and are not directly triggered by server-side events.

D. Scheduled Script Execution (Scheduled Job): Scheduled Jobs are scripts that run at specified times or intervals and are not triggered by events.

For more detailed information, refer to the official ServiceNow documentation on Responding to Events.

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

ServiceNow provides multiple ways to show messages to users in the UI, and the correct method depends on whether the message is meant for the top of the form or next to a specific field. In the GlideForm client API, ServiceNow documents g_form.addInfoMessage(String message) as the method that adds an informational message to the top of the form . This is the standard client-side approach for showing an info banner at the top area of the current form and is commonly used in Client Scripts and UI Policies to inform users about guidance, rules, or results of client-side logic. ServiceNow’s GlideForm documentation specifically names this method and provides examples of its usage via g_form. By contrast, g_form.showFieldMsg() (and similarly named field-message functions) are used to display messages associated with a particular field location, not as a general blue banner at the top of the form. The option g_form.addInfoMsg() is not the documented default method name. Therefore, the correct answer is g_form.addInfoMessage() .

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

" 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

In ServiceNow, the " Allow access to this table via web services " option within the Application Access settings determines whether the table can be accessed through web service protocols, such as REST and SOAP. When this option is selected, it permits the table to be accessible via web services; however, it does not override existing permissions. The user or system making the web service request must still have the appropriate permissions (such as roles and access controls) to perform operations on the table ' s records.

Option A: Incorrect. If the " Allow access to this table via web services " option is not selected, the table is not accessible via web services, regardless of user permissions.

Option B: Correct. Enabling this option allows the table to be accessed via web services, but the user must have the correct permissions to access the table ' s records.

Option C: Incorrect. This option applies to all web service protocols, including both SOAP and REST.

Option D: Incorrect. This option controls overall web service access to the table; specific operations (create, read, update, delete) are governed by user permissions and access controls.

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]

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 REST API is a web service that allows you to interact with the ServiceNow platform using HTTP requests and responses. The ServiceNow REST API supports the following methods:

POST: This method allows you to create a new record or execute an action on the ServiceNow platform. For example, you can use the POST method to create an incident or run a script.

GET: This method allows you to retrieve information from the ServiceNow platform. For example, you can use the GET method to get the details of a user or a table.

DELETE: This method allows you to delete a record or a resource from the ServiceNow platform. For example, you can use the DELETE method to delete an attachment or a workflow context.

PUT: This method allows you to update a record or a resource on the ServiceNow platform. For example, you can use the PUT method to update the state of a task or the value of a system property.

PATCH: This method allows you to update a record or a resource on the ServiceNow platform by sending only the changes. For example, you can use the PATCH method to update the short description of an incident or the order of a module.

The method COPY is not part of the ServiceNow REST API. There is no COPY method in the HTTP protocol. To copy a record or a resource on the ServiceNow platform, you need to use the POST method with the clone action.

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.

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

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()]

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

Ensuring that users receive email notifications in ServiceNow requires verifying specific attributes on the user record:

A. The Email field must have a valid value: This is correct. The Email field should contain a valid email address, as notifications are sent to the address specified in this field.

B. The user must not be locked out: While it ' s important for user access, being locked out does not directly impact the sending of email notifications.

C. The First name and Last name fields must have values: These fields are for identification purposes and do not affect email notification delivery.

D. Active must be true: This is correct. Only active users are eligible to receive email notifications. If a user is marked as inactive, notifications will not be sent to them.

E. Delegation must be enabled: Delegation pertains to assigning responsibilities to another user and does not influence the receipt of email notifications.

For effective email notification delivery, always ensure that the user ' s Email field contains a valid address and that the Active field is set to true.

When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.

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

there are only two types of UX options: Mobile and Classic. Classic is defined as " manage records via lists and form "

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.

Flow Designer is a graphical tool that allows users to automate processes in ServiceNow without coding. The following are supported by Flow Designer:

Call a subflow from a flow. This is a feature that allows users to invoke a subflow, which is a reusable unit of logic, from a flow. This can help simplify complex flows and avoid duplication of logic.

Use Delegated Developer. This is a feature that allows administrators to delegate the development and maintenance of flows and actions to users who are not administrators. This can help distribute the workload and empower non-admin users to create automations.

Run a flow from a MetricBase Trigger. This is a feature that allows users to trigger a flow based on a MetricBase query, which is a way of analyzing time-series data in ServiceNow. This can help automate actions based on data trends and patterns.

The following is not supported by Flow Designer:

Test a flow with rollback. This is not a feature of Flow Designer, but of Automated Test Framework (ATF), which is a tool that allows users to create and run automated tests on ServiceNow applications and features. ATF supports testing flows with rollback, which means reverting any changes made by the flow during the test execution. References: Flow Designer, Automated Test Framework

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.

https://docs.servicenow.com/bundle/tokyo-platform-security/page/administer/contextual-security/concept/access-control-rules.html

The syntax used in a Record Producer script to access values from Record Producer form fields is producer.variable_name. A Record Producer is a type of catalog item that allows users to create records on any table from the service catalog. A Record Producer script is a server-side script that runs when a Record Producer is submitted, and can be used to set values or perform actions on the generated record. The producer object is a global object that represents the Record Producer form and its variables. The variable_name is the name of the variable defined in the Record Producer. References: [ServiceNow Docs - Record producers], [ServiceNow Docs - Record producer script]