Скачать или смотреть ServiceNow Business Rules from Zero to Advanced | Best Practices” part21/100

BusinessRules

(Server side Logic...Runs When record is Inserted,updated,deleted or quiries...Works for UI,API,Import sets,Database level)

1.Interview question:
How do you prevent saving an Incident if the Short Description contains sensitive words like “password”, “secret”, or “confidential”?

2.Why this Question is important?

In production:
Users sometimes enter sensitive information in Short Description
This causes:
Security risks
Data leaks
Audit failures
-This is a very common client requirement
-Interviewers want to check:
String handling in Business Rules
Validation logic
Production-safe code

3.Break the Requirement:
We must STOP SAVE when:
Short Description is not empty
Contains any forbidden/sensitive word
password
secret
confidential

Code must be case-insensitive and handle null values

4.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.