InServiceNow,Business Rulesareserver-side scriptsthat execute when a record is created, updated, deleted, or queried. The"When"setting in a Business Rule determineswhen the rule runs in relation to database operations.
BeforeExecutes before a record is inserted, updated, or deleted.
Used forvalidations, data modifications, and setting field valuesbefore saving.
AfterExecutes after a record has been committed to the database.
Used fortriggering notifications, writing logs, or updating related records.
Async(Asynchronous)Executes after a short delay, allowing the main transaction to complete first.
Used forlong-running processes like API calls, email sending, or external system updates.
DisplayExecutes before the record is sent to the client (UI).
Used topopulateg_scratchpadfor client-side scripts.
The Four Timing Options for Business Rules:
Example Use Cases for Business Rule Timings:Business Rule Timing
When It Runs
Use Case
Before
Before saving to the database
Validate data, auto-populate fields
After
After saving to the database
Send notifications, update related records
Async
Shortly after the transaction completes
Call an external API, send an email
Display
Before the form loads
Pass server data to client-side scripts (g_scratchpad)
A: Insert, Update, Delete, QueryIncorrect- These aredatabase operations, not the execution timing options for Business Rules.
C: Prior to, Synchronous, on UpdateIncorrect- These termsdo not matchthe standard ServiceNowBusiness Rule timing settings.
D: Before, Synchronous, Scheduled Job, ViewIncorrect- "Scheduled Job" isnota Business Rule timing option (it is part ofScheduled Script Executions).
Incorrect Answer Choices Analysis:
ServiceNow Docs - Business Rules Overview#Understanding Business Rules
ServiceNow Docs - Best Practices for Business Rules#Best Practices for Business Rules Official ServiceNow Documentation References: