SNOW-CAD Creating and customizing tables and data — Timed 10 Questions

Question 1

A developer is creating a custom table for tracking hardware assets. The table must have fields for asset tag, serial number, and purchase date. The developer wants to ensure that the asset tag is automatically generated using a prefix followed by an incrementing number. Which approach should the developer use?

Accepted Answer

Create a business rule that calculates the asset tag using a script that increments a counter. Option C is correct because ServiceNow does not have a built-in auto-increment field type, so a business rule must be used to generate a sequential asset tag. The script typically queries the table for the maximum existing number, increments it, and prepends the prefix (e.g., 'AST-0001'). This ensures uniqueness and proper sequencing without relying on sys_id, which is not sequential.

Answer

Use a calculated value that dot-walks to a number table

Answer

Set the default value of the asset tag field to 'AST-' + sys_id

Answer

Configure a dictionary override on the asset tag field to auto-generate

Question 2

An organization has a custom table 'u_incident_task' that extends 'task'. They need to allow users to create records in this table from the 'Incidents' module. The 'u_incident_task' table should appear as a related list on the incident form. However, the related list is not showing the 'New' button. What is the most likely cause?

Accepted Answer

There is no reference field on 'u_incident_task' pointing to the incident table. The 'New' button appears on a related list only when there is a reference field on the target table (u_incident_task) that points back to the source table (incident). Without this reference field, the platform cannot automatically populate the parent record's sys_id when creating a new child record, so it suppresses the 'New' button. This is a core requirement for related list creation in ServiceNow.

Answer

The table is in a different application scope

Answer

The table does not extend 'incident'

Answer

The user does not have the required role

Question 3

A developer needs to create a new table to store custom survey responses. The table should have a field to store the survey name and a field to store the response text. The developer wants to ensure that the table is available in the 'Surveys' application module. Which property must be set on the table?

Accepted Answer

Application module. The Application module property determines which application module a table belongs to, making it visible and accessible within that module's scope. Setting this to 'Surveys' ensures the table appears in the Surveys application module, as required by the developer.

Answer

Application scope

Answer

Table name

Answer

Table label

Question 4

A developer is working with a custom table 'u_project_task' that has a reference field 'u_project' pointing to the 'project' table. The developer wants to create a new field 'u_category' that lists values from a choice list, but the list should be filtered based on the value of 'u_project.u_type'. Which field type should be used?

Accepted Answer

Choice field with a dependent choice list. Option A is correct because a choice field with a dependent choice list allows the list of values in 'u_category' to be dynamically filtered based on the value of another field, in this case 'u_project.u_type'. This is the standard ServiceNow approach for creating cascading or conditional choice lists without custom scripting.

Answer

Choice field with a static choice list

Answer

Calculated value using a script

Answer

Reference field to a table of categories

Question 5

A company has a custom table 'u_employee' with fields: 'first_name', 'last_name', 'department'. They want to create a unique index on the combination of 'last_name' and 'department' to prevent duplicate entries. Where should this index be defined?

Accepted Answer

In the table's dictionary record via the Indexes related list. In ServiceNow, a unique index on a custom table is defined in the table's dictionary record via the Indexes related list. This is the correct location because ServiceNow uses the table's dictionary metadata to manage indexes, and the Indexes related list allows you to specify unique constraints directly on the table definition, ensuring the database enforces uniqueness on the combination of 'last_name' and 'department'.

Answer

In the table schema map

Answer

In the dictionary entry for each field

Answer

In the sys_dictionary table directly

Question 6

A developer needs to create a new table that will store confidential employee feedback. The table must have the following characteristics: (1) Only authorized HR users can read the records. (2) The table should use the 'task' model to leverage assignment and state fields. (3) The table should be accessible via web services for integration. Which TWO actions are required to meet these requirements?

Accepted Answer

Extend the 'task' table. Option D is correct because extending the 'task' table allows the new table to inherit the assignment and state fields required by the 'task' model. This is the standard approach in ServiceNow for creating tables that leverage task-related functionality, such as assignments and workflow states.

Answer

Set the 'table' access policy to 'Internal'

Answer

Extend the 'incident' table instead of 'task'

Answer

Enable the 'Allow web service access' property on the table

Question 7

A developer is creating a custom table 'u_project_risk' to track risks associated with projects. The table must: (1) Automatically set the 'state' field to 'Open' when a new record is created. (2) Prevent deletion of records if the state is 'Closed'. (3) Display a warning message when a user changes the state from 'In Progress' to 'Closed'. Which THREE approaches should the developer use?

Accepted Answer

Set a default value for the 'state' field to 'Open'. Option A is correct because setting a default value on the 'state' field to 'Open' ensures that whenever a new record is created in the 'u_project_risk' table, the field automatically populates with 'Open' without requiring any script or business rule. This is a declarative, low-code approach that leverages the platform's built-in default value functionality at the field level, guaranteeing the requirement is met even if the record is created via web services or import sets.

Answer

Create a before business rule to check state on update

Answer

Define a reference qualifier on the 'project' field

Question 8

A developer created the business rule shown in the exhibit to auto-generate asset tags. However, when a new asset is created, sometimes the generated tag is a duplicate of an existing tag. What is the most likely cause?

Accepted Answer

The query uses 'CONTAINS' which may match unintended tags, and ordering by sys_created_on may not guarantee the highest number. Option D is correct because the script uses a glide query with 'CONTAINS' to find the highest existing asset tag number, which can match unintended tags (e.g., 'TAG-10' matching 'TAG-1001'), and ordering by 'sys_created_on' does not guarantee the highest numeric suffix. This leads to duplicate tags when the generated number is already in use but not detected as the maximum.

Answer

The condition '!current.u_asset_tag' fails when the field is empty

Answer

The script does not account for records with null asset tags

Answer

The script does not handle the scenario when no asset tag exists

Question 9

A developer implemented the client script shown in the exhibit to auto-populate the assigned-to field based on the task type. However, when the task type is changed, the assigned-to field is not updated. The server-side script 'TaskTypeAjax' is correctly defined and returns a valid sys_id. What is the most likely reason for the failure?

Accepted Answer

The Script Include 'TaskTypeAjax' is not client-callable. The client script attempts to call a Script Include named 'TaskTypeAjax' from the client side. By default, Script Includes are not accessible from client scripts unless the 'Client callable' checkbox is enabled in the Script Include record. Since the script is failing to update the assigned-to field, the most likely cause is that 'TaskTypeAjax' is not marked as client-callable, preventing the GlideAjax request from executing successfully.

Answer

The client script does not check if oldValue is different from newValue

Answer

The client script returns on isLoading, preventing execution

Answer

A UI policy is overriding the assigned-to field

Question 10

You are a ServiceNow developer at a large healthcare organization. You have created a custom table 'u_medical_device' to track medical equipment. The table has fields: 'u_device_id' (string), 'u_device_type' (choice: 'Monitor', 'Ventilator', 'Pump'), 'u_location' (reference to 'u_location' table), 'u_status' (choice: 'Active', 'Inactive', 'Maintenance'), and 'u_last_calibration_date' (date). You need to implement a business rule that, when a device's status is changed to 'Maintenance', automatically sets the 'u_last_calibration_date' to the current date and creates a 'u_maintenance_log' record with a reference to the device. Additionally, you want to ensure that only users with the 'medical_device_admin' role can change the status to 'Maintenance'. You have written the business rule but it is not firing correctly. The sys_script table shows the rule is active, order 100, when 'before' query and 'after' update. The condition is: current.status.changes() && current.status == 'Maintenance'. The script sets current.u_last_calibration_date = gs.now(); and creates a GlideRecord for u_maintenance_log. However, the calibration date is not updated, and no log record is created. What is the most likely cause?

Accepted Answer

The business rule is set to run 'before' query instead of 'before' update or 'after' update.. The business rule is configured to run 'before query' and 'after update'. The 'before query' phase fires when a record is retrieved, not when it is updated. Since the script modifies the current record and creates a new record, it must run during an update operation. The correct phases for this logic are 'before update' (to set the date) and 'after update' (to create the log), or a single 'after update' phase. The 'before query' phase prevents the script from executing during the update, causing the calibration date and log record to not be updated or created.

Answer

The script uses 'gs.now()' which returns a date-time string, but 'u_last_calibration_date' is a date field, causing a type mismatch and silent failure.

Answer

The user executing the update does not have the 'medical_device_admin' role, and the business rule lacks an ACL check.

Answer

The condition 'current.status.changes() && current.status == 'Maintenance'' is invalid because 'changes()' returns a boolean and cannot be combined with '=='.