SNOW-CAD Automating application logic with business rules and scripts Practice Test 4 — 15 Questions

Question 1

What is the effect of this business rule?

Accepted Answer

It sets assignment_group to 'IT Support' every time the caller or short description changes.. The business rule is configured to trigger 'on change' for both the 'caller' and 'short description' fields. When either field changes, the rule sets the 'assignment_group' field to 'IT Support'. This is a typical use of a business rule to automatically assign incidents based on field updates.

Answer

It will cause an error because assignment_group is a reference field.

Answer

It only runs when both caller and short description change.

Answer

It only sets assignment_group when the incident is first created.

Question 2

A developer is creating a business rule that should run after a record is inserted or updated. The script should fire on both insert and update. Which condition should be used?

Accepted Answer

current.operation() in ['insert','update']. The `in` operator checks if `current.operation()` matches any value in the list `['insert','update']`, which is the exact requirement for a business rule that should fire on both insert and update. This is the most concise and idiomatic way in ServiceNow to test for multiple operation types.

Answer

current.operation().indexOf('insert') != -1

Answer

current.operation() == 'insert' || current.operation() == 'update'

Answer

current.operation() in ['insert','update','delete']

Question 3

A company uses a business rule to set a field on the Incident table based on the caller's department. However, the rule runs correctly on insert but not on update. The developer suspects the condition is incorrect. The current script uses: if (current.operation() == 'insert' && gs.getUser().getDepartment() == 'IT'). What might be the issue?

Accepted Answer

The condition should check current.caller_id.department instead. The business rule should check the department of the caller associated with the incident record, not the logged-in user. The condition `current.caller_id.department` retrieves the department value from the caller's user record via a dot-walk to the sys_user table, ensuring the rule triggers based on the incident's caller, not the session user. The current script incorrectly uses `gs.getUser().getDepartment()`, which returns the department of the user running the update, which may differ from the caller's department, causing the rule to fail on update.

Answer

The rule is set to run only on insert

Answer

The script uses synchronous business rule instead of asynchronous

Answer

The condition should use current.operation() == 'update' as well

Question 4

A global business rule that runs on after query on the Task table is causing performance degradation. The rule modifies the query condition for all task records. The developer needs to optimize the rule without changing its functionality. Which approach is best?

Accepted Answer

Use glideRecord.addEncodedQuery() instead of addQuery(). Using `glideRecord.addEncodedQuery()` allows the business rule to directly apply a pre-encoded query string to the GlideRecord object, which is more efficient than using multiple `addQuery()` calls. This reduces the overhead of parsing individual conditions and improves performance when modifying query conditions on the Task table, without altering the rule's functionality.

Answer

Move the script to a condition builder script include

Answer

Convert the business rule to a script action in a flow designer

Answer

Make the business rule asynchronous

Question 5

A developer writes a business rule that runs on after update. The script intends to send an email notification when the priority changes. Which method should be used to compare the previous and current values?

Accepted Answer

current.priority.changes(). The changes() method on a field object returns true if the field changed. Option B is correct. Option A checks if any field changed. Option C uses direct comparison but is not a method. Option D uses getDisplayValue which compares labels, not values.

Answer

current.getDisplayValue('priority') != previous.getDisplayValue('priority')

Answer

current.changes()

Answer

previous.priority != current.priority

Question 6

A developer creates a business rule that runs before a record is inserted or updated on the Incident table. The rule sets the assignment group based on the category. However, after the rule runs, the assignment group is not being saved. What is the most likely cause?

Accepted Answer

The rule runs after the record is saved. The most likely cause is that the business rule is configured to run 'after' the record is saved (option B), even though the developer intended it to run 'before'. In a 'before' business rule, changes to fields on the current record are automatically saved when the record is committed. However, in an 'after' business rule, the record is already saved, so modifications to current are not persisted unless the script explicitly calls current.update(). Option A describes a display business rule, which runs client-side and does not affect server-side saving. Option C is unlikely because if it ran on before update only, it would still run before save. Option D is incorrect because setAbortAction(false) is used in 'before' rules to allow the save to proceed, not to persist changes.

Answer

The rule is a display business rule

Answer

The business rule is set to run on before update only

Answer

The script does not use current.setAbortAction(false)

Question 7

A ServiceNow instance has a business rule that runs on after query on the Incident table. The rule adds a condition to the query to filter out incidents with state = 'Closed'. Recently, an update set containing a new business rule was installed, and now the filter is not applied. What might have caused this?

Accepted Answer

The new business rule uses query.setCondition() to set the query condition, replacing the existing condition. The new business rule likely uses query.setCondition() which replaces any existing conditions, including the filter from the existing rule. Option A is less likely because order determines execution sequence, but setCondition replaces. Option B is incorrect. Option D is irrelevant.

Answer

The new business rule has a higher order than the existing rule

Answer

The existing business rule is set to run only on insert

Answer

The new business rule uses glide.addNullQuery

Question 8

A developer is tasked with writing a business rule that should only execute when the record is being updated and the value of the 'state' field changes from 'In Progress' to 'Resolved'. Which condition should be used in the business rule?

Accepted Answer

current.operation() == 'update' && current.state.changesFrom('In Progress') && current.state.changesTo('Resolved'). The changesFrom() and changesTo() methods are the recommended approach for checking field transitions. Options A and D use direct comparison but are less efficient. Option C only checks that state changed, not the specific transition.

Answer

current.operation() == 'update' && previous.state == 'In Progress' && current.state == 'Resolved'

Answer

current.operation() == 'update' && current.state.changes() && current.state == 'Resolved'

Answer

current.operation() == 'update' && current.state == 'Resolved' && previous.state == 'In Progress'

Question 9

A company has a business rule that runs after a record is inserted on the Change Request table. The rule creates a related task record. Recently, the rule stopped working for some users. The developer discovers that the rule fails silently when the logged-in user lacks the 'change_request.create' role. What is the best way to fix this?

Accepted Answer

Set the rule to run as the system user. Setting the business rule to run as the system user bypasses role-based restrictions. Option A would prevent execution. Option C does not handle the error. Option D is unnecessary.

Answer

Use gs.hasRole('change_request.create') to check and abort if false

Answer

Move the script to a script action that runs in the background

Answer

Use current.setAbortAction(false) to ignore the error

Question 10

A developer is creating a business rule that should run on after update of the Incident table. The developer wants to ensure the rule only fires when the incident is assigned to a specific assignment group. Which conditions should be used in the business rule's condition field? (Choose two.)

Accepted Answer

current.operation() == 'update'. `current.operation() == 'update'` ensures the business rule only runs during an update operation on the Incident table. This is the standard way to check the database operation type in ServiceNow business rules, matching the requirement that the rule should fire 'on after update'.

Answer

current.assignment_group.isValidRecord()

Answer

current.assignment_group.changes()

Answer

gs.getUser().getManager() == 'admin'

Question 11

A developer is writing a business rule that should run on after update of the Incident table to send an email notification when the state changes. The developer uses the method current.state.changes() to detect the change. However, the email is sent multiple times for the same incident update. What are two possible reasons? (Choose two.)

Accepted Answer

The email notification is triggered by a different business rule. Duplicate emails on the same incident update occur when multiple business rules send the notification or when the same rule runs multiple times. Option D is correct: another business rule may also be configured to send an email on state change, causing duplicates. Option E is correct: if the business rule runs on both before and after update, it will execute twice for the same update, sending two emails. Option C is incorrect because running on insert causes an additional email on insert, not multiple emails during a single update operation. Option A is incorrect because current.state.changes() properly detects state changes; the issue is not about checking the previous state. Option B is incorrect because setting the condition field to 'state changes' would actually help filter, not cause duplicates.

Answer

The business rule is set to run on every update, but the script does not check the previous state

Answer

The business rule's condition field is set to 'state changes'

Answer

The business rule runs on both insert and update

Question 12

A developer is creating a business rule to automatically assign tasks to a specific group based on the category. The rule is set to run before insert and update on the Task table. The script uses current.assignment_group = 'IT Support'. However, the assignment group is not being set on update even though it works on insert. Which three potential causes should the developer investigate? (Choose three.)

Accepted Answer

The business rule's condition field requires the category to be set. Option A: If the business rule's condition depends on the category field, and the category isn't changed on update, the rule may not run, preventing assignment group update. Option C: If the script only runs on insert but not update, it won't execute on updates. Option E: Another business rule acting after this one could reset the assignment group. Option B: The assignment group being read-only on the form does not stop business rules from setting its value; this is not a cause. Option D: Running only in the global scope does not affect whether the rule runs on update; scope is not a cause.

Answer

The assignment group field is read-only on the form but can be set via business rule

Answer

The business rule is set to run only in the global scope

Question 13

Refer to the exhibit. The business rule is intended to update the CI's operational status when an incident is resolved. However, the CI is not being updated. What is the most likely reason?

Accepted Answer

The script does not include a condition to check if the CI belongs to the cmdb_ci_server table. The script uses `gr.get('cmdb_ci_server', current.cmdb_ci)` which only finds CI records of the 'cmdb_ci_server' table. If the CI belongs to a different class (e.g., 'cmdb_ci_router'), the query returns no record, so the update never occurs. Option B is correct because the script lacks a condition to verify the CI's table class. Option A is incorrect because business rules running after save can still update other records. Option C is false since synchronous rules can update other records. Option D is not the root cause; the `gr.update()` is present, but the problem is that the record is not found.

Answer

The business rule runs after the record is saved, so changes to the CI are not saved

Answer

The business rule runs synchronously, so it cannot update another record

Answer

The script uses gr.update() without checking if the CI record exists

Question 14

In a large enterprise environment, the ServiceNow instance is heavily customized. A business rule on the Change Request [change_request] table runs on after update to initiate a complex workflow involving multiple approvals and updates to Configuration Items (CIs). Recently, the IT operations team noticed that the workflow fails to start for many change requests. The system logs show the error: "Business rule script error: Cannot read property 'sys_id' of null". The developer inspects the business rule script and sees the following code snippet:
var task = new GlideRecord('task');
task.get(current.sys_id);
var relatedCI = task.cmdb_ci;
// The rest of the script uses relatedCI to update the CI's status.
The developer knows that change requests are not stored in the task table; they are in change_request. However, the script was written by a previous developer and has been working for months. The developer must fix the script to ensure the workflow starts correctly. Which action should the developer take?

Accepted Answer

Use current.cmdb_ci directly. Best because current is already the change request record, so current.cmdb_ci is directly available. Option A would work but adds unnecessary database query. Option B would prevent the error but not fix the root cause; the script would still fail to get the CI if the record is not in task. Option D would hide the error but not fix the logic.

Answer

Wrap the script in a try-catch block and log the error then return

Answer

Change GlideRecord('task') to GlideRecord('change_request')

Answer

Add a check if (task.isValidRecord()) before accessing cmdb_ci

Question 15

A mid-sized company heavily relies on ServiceNow for incident management. They have a business rule that runs before insert on the Incident table. The rule dynamically sets the assignment group based on the category of the incident and the location of the caller. To determine the correct group, the script performs a GlideRecord query against a custom table called "u_group_mapping", which contains approximately 5000 records mapping category-location pairs to groups. During peak business hours, when many incidents are created simultaneously, the business rule causes significant delays and occasional timeouts, impacting user experience. The development team has been tasked with optimizing this business rule without changing its functionality. The current script structure is roughly:
(function executeRule(current, previous) {
    var gr = new GlideRecord('u_group_mapping');
    gr.addQuery('category', current.category);
    gr.addQuery('location', current.caller_id.location);
    gr.query();
    if (gr.next()) {
        current.assignment_group = gr.assignment_group;
    }
})(current, previous);
The team wants to reduce the database access overhead. Which optimization technique should the developer implement?

Accepted Answer

Create a script include with a static variable to cache the mapping for the duration of the current transaction. Caching the mapping data in a static variable within a script include ensures that the GlideRecord query against the 5000-record custom table is executed only once per transaction, rather than on every incident creation. This drastically reduces database access overhead during peak hours, as subsequent invocations of the business rule within the same transaction reuse the cached results, eliminating redundant queries and preventing timeouts.

Answer

Use GlideAggregate to retrieve the count of matching groups

Answer

Store the mapping in a global script include variable that persists across sessions

Answer

Move the business rule to run after insert so it does not block the insert