Скачать или смотреть ServiceNow Business Rules from Zero to Advanced | Stop selecting a past delivery date” part 35/100

Custom Table creation & apply on Business Rules



1️⃣ INTERVIEW QUESTION
How do you prevent users from selecting a past delivery date?

2️⃣ WHY THIS QUESTION IS IMPORTANT (REAL PROJECT VIEW)

In real projects:

Delivery cannot happen in the past
Wrong dates break reports, planning, billing
This rule protects data quality

Very common interview + production requirement



3 REQUIREMENT BROKEN INTO 3 SIMPLE STEPS

“User should not save the order if the delivery date is before today.”


Get today’s date
Compare delivery date with today
Stop saving if delivery date is in the past

simple way
Step 1: Get today's date as GlideDate
Step 2: Check delivery date exists and is in the past
Step 3: Stop saving

4. ALTERNATIVE METHODS (WHEN NOT TO USE BR)

 
Method Reason
UI Policy UI only
Client Script Can be bypassed
Flow Designer Heavy for simple rule

👉 Business Rule = BEST

5. Why Business Rule?

Cannot be bypassed
Works from UI, API, import, background
Used in production systems
6. TYPE OF BUSINESS RULE USED


Item Value
Type Business Rule
Table u_amma_organics
When Before
Action Update &Insert
Runs On Server-side


👉 Best practice for validations

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