Automating application logic with business rules and scripts →easyMultiple ChoiceObjective-mapped

SNOW-CAD Practice Question: Automating application logic with business rules and scripts

Exhibit

Refer to the exhibit.

var gr = new GlideRecord('incident');
gr.get('681ccaf9c0a8016400bf7952c6d0a7ef');
gr.setValue('short_description', 'Test update');
gr.update();

Refer to the exhibit. The script runs as a business rule on the incident table. What will happen when this script executes?

⚠ Common exam trap

ServiceNow often tests the misconception that `setValue()` in a business rule will not trigger other business rules, but the default behavior is that it does, unless the 'Don't run other business rules' checkbox is explicitly selected.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The update will trigger other business rules that run on update.

The script uses `setValue()` to update a field on the current record, which is an update operation. In ServiceNow, business rules that run on 'update' will fire when a record is updated, unless the business rule is specifically configured to run 'asynchronously' or with the 'Don't run other business rules' option. Since the exhibit does not show such configuration, the update will trigger other business rules that run on update.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The update will only occur if the business rule condition evaluates to true.
Why it's wrong here
The update() method does not re-evaluate the business rule's condition; it performs the database update.
✓
The update will trigger other business rules that run on update.
Why this is correct
When update() is called, it triggers all business rules set to run on update for that table.
✗
The record will be updated without triggering any other business rules.
Why it's wrong here
update() always triggers business rules; to suppress them, use setWorkflow(false).
✗
The script will throw an error because setValue() requires a third parameter.
Why it's wrong here
setValue() only requires two parameters: field name and value.

Go deeper

SNOW-CAD Practice Question: Automating application logic with business rules and scripts

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question