CAD Certified Application Developer - ServiceNow Questions and Answers

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

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

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.

References:

• [Field types]
• [Date/Time field type]

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

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

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

"Schema map: Provides a graphical representation of the relationships between tables."

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/table-administration/concept/c_TableAdministration.ht ml

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

The following are debugging strategies for client-side scripts, which run in the web browser and manipulate the user interface:

• g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.
• Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.
• jslog(). This is a client-side API that writes a message to the browser console.

The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:

• gs.log(). This is a server-side API that writes a message to the system log. References: Client-Side Scripting APIs, Debugging Client Scripts

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

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

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]

The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:

• source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.
• admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.

The following roles do not grant access to source control repository operations:

• source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.
• git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration. References: Source Control, Source Control Roles

"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

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.

References:

• [Form Designer]
• [Schema map]

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

Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:

• gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole(‘admin’) will return true if the user is an administrator, and false otherwise.
• current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.

The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.

References:

• [Access Control scripts]
• [GlideSystem methods]
• [GlideRecord methods]

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.

The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.

References:

• [Workflow overview]
• [Workflow context]

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

https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedule-report.html Generate and distribute scheduled reports via email.

A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:

• Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
• Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
• Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients.

The following are not true for reports in ServiceNow:

• Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
• All users can generate reports on any table. This is false because users can only generate reports on tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records. References: Reports, Report Security

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

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

"Add instructional text and other design elements to your forms by using form annotations in Form Builder." https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/form-builder/task/create-form-annotations.html

"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

 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

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

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository]

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.

References:

• 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

From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html

g_form.showFieldMsg("field_name", "Hello World", "error"); Puts "Hello World" in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook

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

https://docs.servicenow.com/bundle/rome-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateAModule.html

A module is the functionality within an application menu such as opening a page in the content frame or a separate tab or window. For example, Open is a module under the Problem application menu that opens a list of problem records. Modules are the second level navigation options for applications. Reference: Modules | ServiceNow Tutorials

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

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

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

To link a ServiceNow application to a Git repository, you need to provide the user name, URL, and password of the Git account that hosts the repository12. The URL is the address of the Git repository that you want to link to the application. The user name and password are the credentials that you use to access the Git account. Alternatively, you can use a personal access token instead of a password for increased security3.

References = 1: Link an application to source control - ServiceNow Docs 2: Publish an application to the application repository - ServiceNow 3: Linking an application to Git using a personal access token instead of a password - ServiceNow

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.

References:

• Flow Designer – No-Code Workflows - ServiceNow
• Flow Designer - ServiceNow
• Flow Designer Data Sheet - ServiceNow

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]

 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-platform-administration/page/administer/form-administration/concept/c_FormDesign.html

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

• To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. This will add the field to the form view without changing the table definition.
• To create a new field on a form’s table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. This will create a new column on the table and add the field to the form view.
• To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. This will remove the field from the form view but not from the table definition.

The following statement is false for the Form Designer:

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