CAD Exam Dumps - Certified Application Developer - ServiceNow

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.

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

In the Automated Test Framework (ATF) of ServiceNow, the " Impersonate " test step is used to simulate actions as a specific user. This is crucial for testing functionalities that depend on user roles, permissions, or specific user contexts.

Key Points:

Purpose: The " Impersonate " step allows the test to execute subsequent steps as if performed by the specified user, ensuring that role-based permissions and access controls are accurately tested.

Usage: To add an " Impersonate " step:

Open your test in ATF.

Click on " Add Test Step. "

Select " Impersonate User. "

Choose the user you want to impersonate for the test.

Considerations: Ensure that the user being impersonated has the necessary roles and permissions for the actions being tested. Additionally, be aware that impersonation affects both server-side and client-side operations during the test.

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.

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

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.

" 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