ServiceNow Change Request | Prevent Submit Without CI (Before Business Rule) | 72/100 video series

Описание: 72/100 Business Rules apply on Change Request

"ServiceNow learn Easy By Praveen Amirineni"



How do you prevent a Change Request from being submitted without selecting a Configuration Item (CI)?

Available Methods to Solve This Requirement

🔁 Available Methods (Interview Point)

Method Can Stop Save? Recommended
UI Policy ❌ No Not safe
Client Script ❌ No Can be bypassed
Dictionary Mandatory ❌ Too strict Not flexible
Before Business Rule ✅ Yes ⭐ BEST

Why best?

Server-side validation
Cannot be bypassed
Controls record lifecycle
Used in all real-time Change implementations



Break the requirement into simple steps:

1. Reads the Confguration Item field
2.Checks whether CI(Confguration Item) field is empty
3.Display an error message to user
4.Stops the record from saving.

🌟 Best Practices (Very Important)

Write BR in Global scope for ITSM tables
✔ Use getValue() for safety
✔ Avoid UI-only validations for Change lifecycle

2.Types of Business Rules:

  1.Before : Before the record is saved to the database.

  Make fields mandatory, prevent update, change values before save, Stop duplicate records
  prevent priority downgrade, prevent reopening resolved incident.

  2.After : after
  To trigger actions, To create/update other records, To send notifications,
Changing record after update
 
  3.Aync : after database commit
  Improve performance, heavy logic, long-running scripts, large data updates,
  External integrations, Bulk notifications

  4.Display: when the form is loaded.
  control UI behaviour, pass data to client(g_scratchpad),show warnings, Display VIP banner.