Overview of ServiceNow Business Rules
📌 A Business Rule (BR) is a server-side script that executes when a record is displayed, inserted, updated, deleted, or queried in ServiceNow.
🗄️ All BR records are stored in the `sys_script` table.
🛠️ BRs can automate tasks like automatically updating a field value upon a condition or stopping users from saving records if validation fails.

Types and Processing of Business Rules
🔢 There are four main types of business rules based on execution timing: Before, After, Async, and Display.
⚙️ Every BR involves two steps: When to Run (defining timing and database operation) and Action (defining the task via configuration or scripting).
🔄 Processing order during a form submission involves checking Before rules, updating the database, and then executing After rules.

Actions Executable by Business Rules
✍️ Common actions include updating field values based on other fields, preventing record inserts/updates with invalid data, displaying informational messages upon record insertion, and creating child tasks when a parent record is created.
✅ Many functionalities can be achieved purely through configuration (setting values, defining timing/operations) without writing code.
💻 Scripting is reserved for advanced requirements not achievable through configuration alone, utilizing the 'Advanced' option for server-side scripts.

Global Variables in Business Rule Scripting
*️⃣ Four key global variables are available for accessing record data within scripts:
* `current`: Stores the current state of the record being worked on.
* `previous`: Captures the previous state of the record before the update or deletion occurred.
* `gs.scratchpad`: An object used to pass information to the client, primarily available on 'Display' type BRs.
* `gs.system`: Allows access to various GlideSystem methods for server-side operations.

Configuration vs. Scripting in Practice
💡 A demonstration showed setting the Assignment Group to 'Network Team' when the Category is 'Network' using:
1. Configuration only: Setting conditions in 'When to Run' and defining the action in the 'Actions' tab (best practice).
2. Scripting: Using `current.assignment_group = ` within the script section to achieve the identical result.
🏆 Best Practice: Always attempt to fulfill requirements using configuration first before resorting to scripting, as configuration is simpler and often more stable.

Key Points & Insights
➡️ Business Rules are powerful server-side tools for data validation, automation, and record manipulation in ServiceNow.
➡️ The BR types (Before, After, Async, Display) dictate when the server-side code executes relative to database operations.
➡️ Prioritize configuration over scripting for achieving functionality unless the requirement explicitly demands complex logic or interaction not supported by configuration options.
➡️ Utilize global variables like `current` and `previous` to compare and manipulate field values within server-side scripts.

📸 Video summarized with SummaryTube.com on Nov 26, 2025, 19:05 UTC