In ServiceNow, Business Rules are server-side scripts that execute at specific times relative to database operations. The "When" setting determines when the Business Rule runs in relation to a record action (Insert, Update, Delete, Query).
Why is Option A Correct?✅ Before
Executes before a record is saved to the database.
Used to validate data, modify values, or prevent an action (e.g., stopping an invalid update).
✅ After
Executes after a record is inserted, updated, or deleted.
Commonly used for triggering notifications or creating related records.
✅ Async (Asynchronous)
Runs after a database operation but executes in the background.
Ideal for long-running or performance-heavy tasks (e.g., integrating with external systems).
✅ Display
Executes before a form loads, allowing modifications to fields before they are displayed to the user.
Typically used for pre-filling form fields based on user roles or conditions.
Why Are the Other Options Incorrect?⌠B. Prior to, Synchronous, on Update
"Prior to" is not a valid Business Rule execution timing.
"Synchronous" is a general term but is not a specific execution timing option in Business Rules.
"on Update" is a database operation, not an execution timing.
⌠C. Insert, Update, Delete, Query
These are database operations that trigger Business Rules, not execution timings.
Execution timing determines when (before, after, etc.), while these determine what triggers it.
⌠D. Before, Synchronous, Scheduled Job, View
"Synchronous" is not a Business Rule timing option.
"Scheduled Job" refers to Scheduled Jobs (not Business Rules).
"View" is a UI-related concept, not a Business Rule execution timing.
ServiceNow Business Rules - How They Work
ServiceNow Best Practices - Business Rule Execution Timing
ServiceNow Developer Documentation - Before, After, Async, and Display Business Rules
References to Official Certified System Administrator (CSA) Documentation: