Issue
When running an Update Job in ServiceNow, history and activity records may be created even when system fields are not updated. This often causes confusion when updates appear under a specific user in Form History or Workspace Activities.
Cause
Update Jobs have two key checkboxes:
Auto update system fields
True: Updates system-managed fields such as sys_updated_by and sys_updated_on.
False: Prevents any changes to system-managed fields.Run business rules and engines
True: Executes all Business Rules and related automation (Flows, SLAs, notifications).
False: Skips all Business Rules and automation during the update.
If Run Business Rules is checked, history and audit records can still be created—even when system fields are not updated. These records may display the user who ran the Update Job.
Scenario
Update Job used to modify Watch List
Executed as a normal user
Configuration:
Auto updating system fields - set to false
Run business rules and engines - set to true ✅
Result:
System fields remain unchanged, but history entries are created showing the user who ran the job.
Fixing an Already-Run Update Job
Rollback the Update Job (if available)
Use a fix script to correct data if rollback is not possible
Delete records from (through script):
sys_history_line
sys_history_set
If activity still appears in Workspace, also delete:
sys_audit
sys_audit_value
Update Job – All 4 Checkbox Scenarios
Scenario 1: Silent Update (Recommended for Data Fixes)
Auto update system fields: ❌ False
Run business rules and engines: ❌ False
Result:
No system fields updated
No Business Rules, Flows, or SLAs run
No history or workspace activity
Use when: Data cleanup, Watch List fixes, one-time corrections
Scenario 2: Automation Required (Correct & Recommended)
Auto update system fields: ✅ True
Run business rules and engines: ✅ True
Result:
System fields updated
Business Rules, Flows, SLAs execute
History shows System Administrator (when run as admin)
Use when: Stage changes, SLA cancel/start, Flow execution
Scenario 3: Partial Suppression (Common Issue Scenario)
Auto update system fields: ❌ False
Run business rules and engines: ✅ True
Result:
System fields not updated
Business Rules and Flows run
History/audit records still created
Updates appear under the user who ran the job
Scenario 4: System Fields Only
Auto update system fields: ✅ True
Run business rules and engines: ❌ False
Result:
System fields updated
No Business Rules, Flows, or SLAs
Limited audit visibility
