SNOW-CAD Application development using ServiceNow Studio — 10 Questions

Question 1

A developer is troubleshooting a business rule in a scoped application that is not triggering. The rule is set to run 'before' query, with condition 'current.state == 1'. The table has read ACLs that restrict access. What is the most likely reason the business rule is not executing?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The user does not have read access to the records, so the query does not execute the rule.. Business rules that run 'before query' execute when a query is made against the table. If the user lacks read access due to ACL restrictions, the query itself is not permitted, so the business rule never triggers. This is because the platform's security layer evaluates ACLs before executing business rules, preventing the rule from running when the user cannot read the records.

Answer

The condition 'current.state == 1' is incorrect syntax.

Answer

Another business rule with higher order is preventing execution.

Answer

The business rule is scoped and cannot access the table.

Question 2

A developer is building a custom application that requires a scheduled job to run every hour and check for overdue tasks. In ServiceNow Studio, what is the best way to implement this?

Accepted Answer

Create a Scheduled Job in Studio that runs every hour and executes a script to check overdue tasks.. ServiceNow Studio provides a native 'Scheduled Jobs' module that allows developers to create and manage recurring server-side scripts directly within the IDE. This approach leverages the platform's job scheduler, which runs on the node's clock and integrates with the glide system, ensuring reliable hourly execution without external dependencies or performance overhead from transactional triggers.

Answer

Set up a REST API endpoint that external cron jobs call every hour.

Answer

Create a Business Rule that runs on 'after' insert and update to check for overdue tasks.

Answer

Use Flow Designer to create a scheduled flow that runs every hour.

Question 3

A developer is creating a scoped application and needs to reference a global table (e.g., 'sys_user') from a business rule. Which TWO statements are true regarding cross-scope access?

Accepted Answer

To write to a global table, the application must be granted the 'global' scope or have appropriate ACLs.. Scoped applications operate within an access control framework that restricts direct writes to global tables. To write to a global table like 'sys_user', the application must either be granted the 'global' scope (which removes scoping restrictions) or have appropriate ACLs that explicitly allow the write operation. Without these, a scoped application's GlideRecord write will fail due to cross-scope access controls enforced by the ServiceNow platform.

Answer

Scoped applications can create records in global tables via GlideRecord without restrictions.

Answer

Scoped applications can call global script includes by default.

Answer

Scoped applications can update global tables without any additional configuration.

Question 4

A developer encounters this error when running a business rule in a scoped application. The table 'x_myapp_incident' was created in the application scope and has records in it. What is the most likely cause?

Accepted Answer

The table was removed from the application scope after creation.. When a table is removed from an application scope after creation, the table still exists in the instance but is no longer associated with the application. Business rules running in the scoped application cannot access tables that are not part of the application's scope, causing an error. This is because scoped applications enforce strict table visibility rules, and only tables explicitly included in the application scope are accessible.

Answer

The ACLs on the table restrict access for the script's user.

Answer

The business rule is trying to access a table in a different scope without using the 'global.' prefix.

Answer

The application was installed via an update set and the table was not included.

Question 5

A developer is building a custom application in ServiceNow Studio. The application requires a table that stores incident-like records but with additional custom fields. The developer wants to leverage existing functionality such as assignment rules, escalation, and SLA tracking. Which approach should the developer take?

Accepted Answer

Extend the Incident table and add custom fields to the extended table.. Extending the Incident table (Option A) is correct because it allows the developer to inherit all existing Incident functionality—such as assignment rules, escalation, and SLA tracking—while adding custom fields. In ServiceNow, table extension creates a child table that inherits all business rules, ACLs, and workflows from the parent, ensuring the custom application leverages the full Incident lifecycle without reimplementation.

Answer

Clone the Incident table and rename it, then modify the clone.

Answer

Create a new table from scratch and manually add all necessary fields and business rules.

Answer

Use the Configuration Management Database (CMDB) to store the records.

Question 6

A developer is building a custom application in ServiceNow Studio for IT asset management. The application includes a table 'Asset' with fields: asset_tag (string), serial_number (string), purchase_date (date), cost (currency), and status (choice: In Use, In Stock, Retired). The developer needs to create a business rule that automatically sets the status to 'Retired' when the cost is zero and the purchase_date is older than 5 years. The business rule should run before the record is saved to the database and should not prevent the save if conditions are not met. The developer writes the following business rule in Studio: Table: Asset, When: Before, Order: 100, Condition: current.cost == 0 && current.purchase_date < gs.yearsAgoStart(5). The script is: current.status = 'Retired'; However, the status is not being updated as expected. What is the most likely issue?

Accepted Answer

Replace gs.yearsAgoStart(5) with gs.yearsAgo(5) to get the exact date 5 years ago.. The issue is that `gs.yearsAgoStart(5)` returns the start of the year (January 1st) five years ago, not the exact date five years ago. This means a record with a purchase_date that is, for example, 5 years and 1 month old might still be after that start-of-year date and thus not match the condition. The correct method is `gs.yearsAgo(5)`, which returns the exact date and time five years ago, ensuring the comparison works as intended for any purchase_date older than 5 years.

Answer

Replace gs.yearsAgoStart(5) with gs.yearsAgoEnd(5) to get the end of the year 5 years ago.

Answer

Change the table from 'Asset' to 'Asset [new]' as the business rule may be on the wrong table.

Answer

Increase the order of the business rule to 200 to ensure it runs after other rules.

Question 7

Match each ServiceNow scripting API to its function.

Accepted Answer

GlideRecord: Perform CRUD operations on database tables. The correct matches are: GlideRecord for CRUD operations, GlideSystem for system properties/IDs, and GlideAggregate for aggregate calculations. Common confusions involve swapping the functions of GlideAggregate, GlideDateTime, and GlideUser.

Answer

GlideRecord: Used to perform aggregate calculations

Answer

GlideSystem: Used to manipulate date and time values

Answer

GlideAggregate: Used to access user session information

Question 8

A company needs to create a new application in ServiceNow Studio. What is the correct first step?

Accepted Answer

Open Studio from the left navigation menu, then click 'Create Application'.. In ServiceNow, the correct workflow to create a new application is to open ServiceNow Studio (from the Application Navigator or the left navigation menu) and then click 'Create Application'. Studio is the dedicated development environment for building scoped applications, and 'Create Application' is the entry point within it.

Answer

Navigate to System Applications > Studio and click 'Create Application'.

Answer

Use the Application Navigator to create a new application.

Answer

Go to Application Files > New and select 'Application'.

Question 9

A developer is troubleshooting a client script that hides a field on a form when a condition is met, but it is not working. The script is attached to the 'g_form' object in Studio. What is the most likely reason?

Accepted Answer

The client script is set to run on the 'Load' event instead of 'Change'.. The most likely reason because client scripts that need to react to a condition change must be set to run on 'Change' event rather than 'Load'. If the script runs only on 'Load', it executes once when the form loads and will not re-run when the condition changes, so the field remains visible. Option B is incorrect because the API for hiding fields (e.g., g_form.setVisible) is not deprecated. Option C is incorrect because client scripts do not have a 'Run As' role; that applies to server-side scripts. Option D is incorrect because client scripts can access any field present on the form regardless of the field's scope.

Answer

The script is using a deprecated API.

Answer

The script is not running due to a missing 'Run As' role.

Answer

The field is not part of the application scope.

Question 10

In ServiceNow Studio, which role is required to create a new scoped application?

Accepted Answer

Admin role. In ServiceNow, the admin role is required to create a new scoped application via ServiceNow Studio. Scoped applications are isolated development environments with their own namespace, tables, and access controls, and creating one requires elevated privileges that only the admin role provides by default. This ensures governance over the application namespace and prevents unauthorized customizations from polluting the instance.

Answer

A global scope update set

Answer

No special role; any user can create applications

Answer

Application Creator role