#3 What is After Business Rule in ServiceNow | End to end Tutorial of Business Rules in ServiceNow

After Business Rule Fundamentals
📌 An After Business Rule triggers only after the user submits a form and the record is successfully saved to the database.
📌 Key use cases include: showing a message upon record creation, creating associated records (like Problem Tasks), deleting related records after a parent deletion, or updating work notes based on parent updates.
📌 Business rules can be configured without scripting for simple actions, but scripting is often necessary for dynamic updates, especially in `after update` scenarios.

After Business Rules Without Scripting (Configuration Only)
⚙️ For an After Insert operation, configuring an action to "add a message" successfully displays a confirmation to the user upon story creation (e.g., "You have created new story").
⚙️ For After Update scenarios (e.g., Priority changes to P1), direct field updates via configuration are insufficient; they require scripting, specifically using `current.setWorkflow(false)` followed by `current.update()` to avoid triggering other business rules unnecessarily.

After Business Rules With Scripting
🖥️ Using scripting in After Insert allows for dynamic messages, such as appending the newly generated record number using `gs.addInfoMessage("... " + current.number);`.
🛠️ Scripting is essential for complex actions like creating child records; for example, an After Update rule where changing the story state to "Work in Progress" automatically creates a new record in the `rm_scrum_task` table using `GlideRecord` operations (`gr.initialize()`, `gr.insert()`).

Key Points & Insights
➡️ For updates in an After Business Rule, use `current.setWorkflow(false)` before `current.update()` to prevent infinite loops or unnecessary execution of subsequent business rules.
➡️ Configuration-only business rules are limited to static changes; scripting (`gs.addInfoMessage`) is required to access and display dynamic record values like `current.number`.
➡️ Creating related records based on parent updates (e.g., creating a Scrum Task when the Story state changes) is a primary function best achieved using `GlideRecord` within an After Update script.

📸 Video summarized with SummaryTube.com on Nov 26, 2025, 21:35 UTC