Business Rules Questions

Create and manage business rules for server-side automation. Understand when business rules execute, how to use conditions and scripts, and best practices for server-side logic.

24 total questions2 free questions

Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made

About Business Rules

Business Rules are server-side scripts that execute when database records are displayed, inserted, updated, deleted, or queried. They are one of the most powerful automation tools in ServiceNow, allowing developers to enforce data policies, automate workflows, and implement complex business logic.

Why This Matters for Your Exam

Questions focus on understanding the different types of business rules (before, after, async, display), when each type executes, and how to use the current and previous objects effectively.

Key Concepts to Master

Understand the four types of business rules and their execution order. Know how to use conditions vs scripts for rule logic. Learn when to use before rules (data validation/modification) vs after rules (related record updates) vs async rules (heavy processing).

Exam Tips

Remember that 'before' business rules can modify the current record without an explicit update() call, while 'after' rules require update() for changes to related records. Know that 'display' business rules run when a form loads and can set scratchpad values for client scripts.

Practice Questions

24 questions available
1
application

A developer adds validation to a business rule on the Incident table. A colleague asks whether it also applies when incidents are updated from a list or through a web service, not only from the form. Where does the rule run, and what does that mean here?

AIn the user's browser, so it applies just while a form is edited
BAs a database trigger, so it fires even when GlideRecord is bypassed
COn the server, so it applies to forms, lists, and web services
DOn a MID Server, so it covers integration traffic but not forms

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. On the server, so it applies to forms, lists, and web services

A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. Because it runs on the server, it applies consistently whether the record is accessed through a form, a list, or a web service, which is a key difference from client scripts.

  • Why A is wrong: Running only while a form is edited describes client scripts, which run in the browser. The docs contrast this with business rules, which run on the server for any access path.
  • Why B is wrong: Business rules are not database triggers. The docs state they run only when record operations are called through the GlideRecord API, so bypassing GlideRecord skips them.
  • Why D is wrong: A MID Server is a Java application on the local network that moves data between the instance and external systems; it is not where business rules execute.
2
knowledgeSelect all that apply

A developer is configuring when a new business rule should run in relation to the database operation. Which of these are valid values for that setting? (Select all that apply)

ABefore
BAsync
CAfter
DDeferred

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Before; B. Async; C. After

The docs list the options for when a business rule runs relative to the database operation as Before, After, Async, and Display. Before runs after the form is submitted but before the database action, After runs after the database action, and Async runs after the scheduler runs a job created from the rule.

  • Why D is wrong: Deferred is not one of the documented When options. Delayed background processing is handled by the Async option, which runs after the scheduler runs the job created from the rule.