Debugging business rules
Quick answer
When a business rule misbehaves, work through this checklist.
When a business rule misbehaves, work through this checklist.
- Confirm the When (before/after/async) and the condition match.
- Check the order field, a lower-order rule may change data first.
- Add
gs.info()logging and watch the system log. - Verify the rule is active and in the right scope.
- Watch for recursion from
current.update().
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What controls which rule runs first?
- A. The order field
- B. The sys_id
- C. The caller
Show answer
A. The order field
Lower order runs earlier.
What causes recursive rules?
- A. current.update() in the rule
- B. gs.info()
- C. A UI policy
Show answer
A. current.update() in the rule
Updating the same record re-triggers the rule.
Frequently asked questions
What does the term Debugging business rules refer to in ServiceNow?
When a business rule misbehaves, work through this checklist.
What is the practical takeaway on Debugging business rules?
Confirm the When (before/after/async) and the condition match. Check the order field, a lower-order rule may change data first. Verify the rule is active and in the right scope.