After Business Rule Modifications
A developer has created a Business Rule that runs on the 'After' order of the incident table. The Business Rule modifies several fields on the incident record. After testing, the developer notices that the changes are not being saved to the database. What is the most likely cause?
Quick Answer
The answer is that the Business Rule does not include a call to current.update() after making field changes. This is because a Business Rule configured to run on the 'After' order executes after the database operation has already completed, meaning any field modifications made to the record in memory will not automatically persist to the database. The developer must explicitly invoke `current.update()` to save those changes; without it, the modifications are discarded once the script finishes. On the ServiceNow Certified Application Developer CAD exam, this concept tests your understanding of the Business Rule execution order and the critical distinction between 'Before' rules (which auto-save) and 'After' rules (which require manual persistence). A common trap is assuming all field changes in a Business Rule are automatically saved, so remember the mnemonic: "After actions need an update action."
⚠ Common exam trap
Watch out — candidates often assume any field changes in a Business Rule are automatically saved, failing to distinguish between 'Before' (auto-save) and 'After' (requires explicit `current.update()`) execution order.
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 Business Rule does not include a call to current.update() after making field changes.
In ServiceNow, a Business Rule set to run 'After' the database operation does not automatically save field changes to the database. The developer must explicitly call `current.update()` to persist the modifications. Without this call, the changes exist only in memory during the script execution and are discarded after the rule completes. Option D is incorrect because the rule is specifically set to run 'After' as stated in the stem; if it were 'Before', changes would be saved automatically without needing `current.update()`. Options A and C are possible but less likely; the most common cause is the missing `current.update()` call.
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 Business Rule is disabled for the current user's role.
Why it's wrong here
Incorrect: If disabled, the rule wouldn't run at all, so changes wouldn't even be attempted.
- ✓
The Business Rule does not include a call to current.update() after making field changes.
Why this is correct
Correct: After Business Rules require explicit current.update() to save changes.
- ✗
The fields being modified are read-only due to a data policy.
Why it's wrong here
Plausible but not most likely; read-only fields would prevent modification entirely, but the rule might still work if allowed.
- ✗
The Business Rule is set to run on 'Before' instead of 'After'.
Why it's wrong here
Incorrect: If it were set to Before, changes would be saved automatically; but the rule is After.
Go deeper
Related to this question
About these practice questions
One of 481 original SNOW-CAD practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SNOW-CAD
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company has a Business Rule that runs after a record is updated. The rule needs to update a related record on a different table. However, the related record update is not being saved. What is the most likely cause?
medium- A.There is a script error that is being ignored because the Business Rule is set to 'true' for 'Run asynchronously'.
- ✓ B.The script is missing the .update() method on the GlideRecord object after setting field values.
- C.The Business Rule runs in a separate transaction and the update is rolled back.
- D.The user running the script does not have write access to the related table.
Why B: In ServiceNow, when a Business Rule modifies a GlideRecord object (e.g., setting field values on a related record), the changes are not persisted to the database until the `.update()` method is explicitly called. Without `.update()`, the script runs without error but the modifications are lost, which is the most common cause of an update not being saved.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.