ServiceNow CAD - Certified Application Developer - ServiceNow

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]

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 welcome screen appears every time a new application is created through the Guided Application Creator. The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app. Reference: Guided App Creator

Application Access settings in ServiceNow control which operations are permitted on a table by other applications. The following operations can be restricted:

Query (A) - Valid: Controls whether other applications can read (query) records from the table.

Create (B) - Valid: Determines whether other applications can add new records to the table.

Execute (C) - Incorrect: No such operation exists for Application Access.

Update (D) - Incorrect: "Update" permissions are controlled through Access Control Lists (ACLs), not Application Access settings.

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

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

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