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

Question 1

A developer writes a before-update business rule on the Incident [incident] table that must copy a value from a custom field on the caller's User [sys_user] record into the incident. During testing, the value is written on the first update but subsequent updates leave the field empty. The script reads: `var gr = new GlideRecord('sys_user'); gr.get(current.caller_id); current.u_dept = gr.u_dept;` and the rule has no condition and no filter. Which change resolves the empty value while keeping the rule on the incident table?

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

Accepted Answer

Rename the local GlideRecord variable so it does not shadow the global `current` object, then re-query the user record inside the rule.. In a before business rule the platform exposes the triggering record through the global `current` object, and any script-level variable that reuses that name shadows the platform reference for the remainder of the transaction. When the rule runs a second time, the shadowed object no longer points at the Incident, so caller_id is undefined and the copied value is empty. Renaming the local GlideRecord and re-querying the user restores consistent behavior while keeping the rule on the incident table.

Answer

Add a condition `current.caller_id.changes()` to the business rule so it only fires when the caller changes.

Answer

Change the business rule's When setting to 'after update' and add `current.update()` after the assignment.

Answer

Convert the assignment to `current.setValue('u_dept', gr.u_dept)` and keep the original GlideRecord variable name.

Question 2

A developer creates a before query business rule on the Incident [incident] table to restrict records based on the caller's department. After deployment, users report that the incident list is empty, even though they should see records for their department. The business rule script includes a condition that checks if the user is not in the 'ITIL' role and then calls current.addQuery('department', user.department). What is the most likely cause of the empty list?

Accepted Answer

The business rule is adding a query condition that conflicts with an existing ACL or domain separation, resulting in no visible records.. Before query business rules modify the query before it executes. When they add conditions that are too restrictive or conflict with existing ACLs or domain separation, the resulting query may return no records. In this case, the combination of the department filter and existing security constraints likely filters out all incidents for the affected users.

Answer

The user object does not have a 'department' field, causing the query to fail and return no records.

Answer

The business rule is executing on the wrong table, so the query is applied to a different table and returns no results.

Answer

The business rule is missing a 'return' statement after adding the query, causing the query to be ignored.

Question 3

A developer is writing an after update business rule on the Problem [problem] table to create a related Change Request when the problem state changes to 'Fix in Progress'. The business rule must avoid creating duplicate change requests if one already exists. Which two approaches should the developer use to reliably prevent duplicate change requests? (Choose two.)

Accepted Answer

Use a GlideRecord query to check for existing change requests linked to the problem before inserting a new one.. To reliably prevent duplicate change requests, the developer should both check for existing records via a GlideRecord query and enforce a unique constraint at the database level. The query handles most cases, while the unique constraint provides a safety net against race conditions. Together, they ensure duplicates are avoided even under concurrent updates.

Answer

Use the 'current' object to check if a change request already exists in the same transaction.

Answer

Use a before query business rule to block duplicate change request queries.

Answer

Set the business rule to run asynchronously to avoid race conditions.

Question 4

A developer needs a business rule to run only when the 'state' field of a Problem [problem] record changes to 'Closed'. The rule must not fire when other fields are updated. Which condition should be used?

Accepted Answer

previous.state != current.state && current.state == 'Closed'. To detect a transition into a specific value, a business rule must compare the previous and current values and then confirm the target value. The expression previous.state != current.state ensures the field changed, and current.state == 'Closed' ensures it changed to Closed. This prevents the rule from firing on unrelated updates while state remains Closed.

Answer

current.state.changesTo('Closed')

Answer

previous.state == 'Closed'

Answer

current.state == 'Closed'

Question 5

A developer creates an after update business rule on the Incident [incident] table that calls gs.eventQueue() to notify an external system whenever the 'priority' changes. During testing, the external system receives duplicate events for a single priority change. The business rule condition is 'current.priority.changes()'. What is the most likely cause of the duplicate events?

Accepted Answer

The business rule is executing more than once in the same transaction, for example because it is triggered by a related update or a second save, so the event is queued each time.. Duplicate events occur because the after update rule runs more than once during the same transaction, and each run sees a priority change and queues the event. The changes() condition itself is correct for detecting a change, but it does not prevent multiple executions. Ensuring the rule runs only once, or guarding the event with a flag, eliminates the duplicates.

Answer

Another business rule or workflow is also queuing the same event, causing the event to be registered twice.

Answer

The changes() method returns true on every update after the first change because it compares against the last saved value, so subsequent updates re-queue the event.

Answer

The business rule is set to run on both insert and update, so it fires twice.

Question 6

A developer needs to create a business rule that runs only when a new record is inserted into the Task [task] table and the 'priority' field is set to '1 - Critical'. The business rule should also send an email notification. Which business rule configuration should the developer use?

Accepted Answer

After insert, with a condition 'priority=1', and an email notification triggered by the business rule using gs.eventQueue.. The business rule must run on insert, so 'after insert' is appropriate. It should check the priority condition and then use gs.eventQueue to trigger an email notification. This ensures the record is fully saved and the notification is processed asynchronously, which is the recommended pattern.

Answer

Before update, with a condition 'priority=1', and an email notification sent directly from the business rule.

Answer

After update, with a condition 'priority=1', and an email notification sent via a notification record.

Answer

Before insert, with a condition 'priority=1', and an email notification sent via a separate notification record.

Question 7

A developer writes an after insert business rule on the Incident [incident] table that updates the same incident record by setting a custom field. The rule causes a recursive loop and the instance becomes unresponsive. Which approach best prevents the recursion?

Accepted Answer

Set the business rule's 'When' to after insert but add a filter condition that checks the field is empty, and update the record using a GlideRecord update that does not trigger the same rule.. Recursion in an after insert business rule typically occurs when the rule updates the same record, causing the rule to fire again. Adding a condition that the field is empty ensures the rule runs only once, because after the update the condition is no longer met. Since the rule is scoped to insert, the subsequent update does not trigger it again, breaking the loop.

Answer

Use a before update business rule instead and set the field directly on current without performing an update.

Answer

Change the business rule to before insert so the update happens before the record is saved.

Answer

Add a condition to the business rule that checks a flag or uses current.setWorkflow(false) before the update.

Question 8

A developer writes an after update business rule on the Incident [incident] table that calls a script include to update a related record on the Problem [problem] table. The script include uses GlideRecord to query and update the problem. During testing, the developer notices that the problem record is not being updated, and the system log shows an error: 'Illegal attempt to update problem record in an after update business rule.' What is the most likely cause?

Accepted Answer

The script include is using GlideRecord to update the problem record without setting 'setWorkflow(false)', causing the update to be blocked.. The error occurs because the after update business rule attempts to update a related problem record, which can cause recursive business rule execution. To avoid this, the developer should use setWorkflow(false) on the GlideRecord update to prevent triggering business rules on the problem table. This is a common pattern when updating other records from a business rule.

Answer

The business rule is running in an after update context, which prohibits updating other records due to potential recursion.

Answer

The script include is missing a 'gs.include' statement, so it is not loaded correctly.

Answer

The script include is not set to client callable, so it cannot be invoked from a business rule.

Question 9

A developer is troubleshooting a before update business rule on the Incident [incident] table that is supposed to set the 'assignment_group' when the 'category' changes to 'software'. The rule does not seem to fire. Which two configuration checks should the developer verify? (Choose two.)

Accepted Answer

Verify that the business rule's condition field or script condition evaluates to true for the record being updated.. When a before update business rule does not fire, the first checks are whether it is configured for the before timing with the update operation enabled, and whether its condition or script condition evaluates true for the record. These two settings directly determine whether the rule executes. Form layout, choice values, and abort interference are secondary and do not directly explain a rule that never runs.

Answer

Ensure the 'assignment_group' field is included in the form layout for the incident table.

Answer

Check that the 'category' field has a choice value of exactly 'software' and that the rule script compares against that value.

Answer

Confirm the business rule is active and its order is not being overridden by another rule that aborts the transaction.

Question 10

A developer is troubleshooting a before business rule on the Change Request [change_request] table that is supposed to set the 'assignment_group' based on the 'category' field. The business rule is active and has no conditions, but it is not firing. The developer confirms that the 'category' field is being updated. What is the most likely reason the business rule is not executing?

Accepted Answer

The business rule is set to run in a different scope, and the change_request table is not in that scope.. Business rules in scoped applications only run on tables within their scope or on tables they have been granted access to. If the change_request table is in the global scope and the business rule is in a custom scope without cross-scope access, the rule will not fire. The developer should check the application scope and access settings.

Answer

The business rule is set to run before update, but the 'category' field is not included in the 'set' of fields that trigger the rule.

Answer

The business rule is missing a condition, so it is not filtering correctly.

Answer

The business rule is set to run on insert only, and the update is not triggering it.

Question 11

A developer is writing a business rule on the Incident [incident] table that runs Before Update. The rule must perform two validations: (1) prevent the state from being changed to 'Closed' if there are open child incidents, and (2) ensure that the 'close_notes' field is not empty when the state is 'Closed'. The developer wants to abort the save if either validation fails and display an error message to the user. Which two script snippets should the developer include in the business rule to achieve this? (Choose two.)

Accepted Answer

var child = new GlideRecord('incident'); child.addQuery('parent', current.sys_id); child.addQuery('state', '!=', 8); child.query(); if (child.hasNext()) { gs.addErrorMessage('Cannot close with open child incidents.'); current.setAbortAction(true); }. The correct snippets are those that properly implement the two validations. One snippet must check for open child incidents and abort if any exist. The other must check that close notes are provided when closing and abort if not. Both must use setAbortAction(true) to prevent the save and gs.addErrorMessage() to inform the user. The snippets that use the wrong message type or incorrect filters do not meet the requirements.

Answer

if (current.state.changesTo(8) && current.close_notes.nil()) { gs.addInfoMessage('Close notes are required.'); current.setAbortAction(true); }

Answer

if (current.state.changesTo(8)) { var child = new GlideRecord('incident'); child.addQuery('parent', current.sys_id); child.query(); if (child.getRowCount() > 0) { gs.addErrorMessage('Cannot close with child incidents.'); current.setAbortAction(true); } }

Answer

if (current.state == 8 && current.close_notes == '') { gs.addErrorMessage('Close notes are required.'); current.setAbortAction(false); }

Question 12

A company needs to automatically update the 'Assignment group' field on the Change Request table to 'Change Management' when the 'Category' field is set to 'Network'. Which type of business rule should be used?

Accepted Answer

Before business rule. A Before business rule (Option D) is correct because it runs before the record is saved to the database, allowing you to set the 'Assignment group' field value based on the 'Category' field before the insert or update operation completes. This ensures the assignment group is correctly populated in the same database transaction, avoiding the need for a separate update.

Answer

Display business rule

Answer

Async business rule

Answer

After business rule

Question 13

A developer creates a business rule on the Incident table that executes a GlideRecord query to update related records. The rule runs on 'after' update and queries the Problem table to set a field. However, the update is not being committed. What is the most likely reason?

Accepted Answer

The GlideRecord query requires an explicit gr.updateMultiple() or gr.commit() to persist changes.. In ServiceNow, when a GlideRecord query is used in an 'after' business rule to update records on another table, the changes are not automatically committed. The developer must explicitly call gr.updateMultiple() to persist updates to multiple records, or gr.update() for a single record. Option B correctly identifies this requirement, as the update is not being committed without an explicit method call.

Answer

The developer forgot to use gr.insert() instead of gr.update().

Answer

After business rules cannot update other tables.

Answer

The query returns more than 100 records, causing a governor limit.

Question 14

A company has a business rule on the Task table that runs on 'before' insert. The rule uses current.gotoField('short_description') and current.setValue('short_description', 'Default'). The rule is ordered to run at 500. However, a second business rule on the same table with order 100 also sets the short_description. What will be the final value of short_description?

Accepted Answer

'Default'. Business rules execute in ascending order based on their 'order' field. The rule at order 100 runs first and sets the short_description. Then the rule at order 500 runs and overrides that value with 'Default' using current.setValue(). Since both are 'before' insert rules, the final value written to the database is the one set by the last-executed rule, which is order 500.

Answer

Both values will be concatenated

Answer

The value set by the rule at order 100

Answer

The field will be empty because gotoField() clears it

Question 15

Which TWO of the following are valid ways to trigger a business rule? (Choose two.)

Accepted Answer

Insert. Business rules in ServiceNow can be triggered by database operations such as Insert and Update. These are the core 'when to run' conditions that fire the rule before or after a record is created or modified in the database. Options B and D are correct because they directly correspond to these fundamental database operations.

Answer

Form load

Answer

Timer event

Answer

Inbound email receipt