Job Switch Kit: Everything you need to crack your next ServiceNow interview Get Job Switch Kit →
Get the complete ServiceNow interview prep system — 500+ Q&A, mock interviews & more Get Job Switch Kit →

ServiceNow Business Rule Interview Questions 2026

What are Business Rules? What are the different type of Business Rules?

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.

There are 4 type of business rules.
1. Display BR.
2. Before BR.
3. After BR.
4. Asynch BR.

What is the difference between after and asynch BR?

After BR : This type of BR is used when some field changes needs to be reflected immediately after user saves the record. Mostly used to update/insert record into another table once insert/update/delete operation is performed on current record.

Below is an example where After BR can be used
- On reassignment of incident, add comments in associated problem record.

Asynch BR : As name suggest, it runs asynchronously. Whenever Asynch BR is triggered, system creates new entry in event queue to process. Execution time varies for Asynch BR based on the load on event queue.

What are the different objects accessible in BR?

- Current
- Previous
- gs
- g_scratchpad

Note: Previous object is null in Asynch BR, as there could be multiple updates on same record while BR is in queue for execution which might create conflict on which version needs to be considered as previous.

What is display BR? When to use it? Explain with real time use case?

Display rules are processed when a user requests a record form. The data is read from the database, display rules are executed, and the form is presented to the user.

The primary objective of display rules is to use a shared scratchpad object, g_scratchpad, which is also sent to the client side as part of the form. This can be useful when you need to build client scripts that require server data which is not typically part of the record being displayed.

Real time use case : If logged in user is member of current assignment group then only show description field.

We can write display BR as shown below to check if logged in user is part of current group or not and store result in g_scratchpad object, which later can be accessed in client script to show/hide description field accordingly.

Display BR configuration details :


Display BR Script :


On Load Client Script :

What is query BR? What is primary objective of it? Explain it with real time use case?

Before query business rule gets executed whenever query made to the database on particular table.

The primary objective of query BR is to hide/show records, this could be based on conditions.

Real time use case : Show only active users to all users who is not having admin or user_admin role.

Below BR is OOTB, it checks if user has admin or user_admin role, if yes then it shows all user records else shows only active users.

BR configuration:


BR Script :

What is the difference between query BR and ACL?

1.Query business rules only apply for read access at the row level while ACLs can do CRUD operation at the row and column level.

2. Query BRs will affect a GlideRecord query result where ACLs will not unless we are using GlideRecordSecure class.

3. Query BR shows only those records where filter criteria matched while ACL shows all pages with the restricted records being invisible and a message at the bottom 'some records removed due to security'.

What are global Business Rules?

A global Business Rule is a Business Rule where the selected Table is Global. Any other script can call global Business Rules. Global Business Rules have no condition or table restrictions and load on every page in the system.

Note : The reason we would need to use Global Business rules in the past is if we wanted a custom globally accessible function, such as getMyGroups, or getUser. Now a days we can do the same thing in Script Includes which has less performance impacting way.

How to prevent form submission via Business Rule?

We can use 'current.setAbortAction(true)' in Business Rule script to abort action. This will stop data updation in database.

How to identify if current operation is insert, update or delete in Business Rules?

We can use current.operation() in BR. Depending on current operation, it returns update, delete or insert value.

How to trigger notification via Business Rules?

We can use gs.eventQueue method to trigger notification via business rule.
Syntax : gs.eventQueue('event_name',current,'param1','param2');

What is the result data if we filter only active records through Query BR and add reference qualifier with active =false condition?

It will show 0 records, since query BR gets executed whenever query made to the table which will return only active records and as reference qualifier is adding active =false filter, system will show 0 records.

Assignment for you:

1. Which type of BR shouldn't include current.update() and why?

2. Explain advantages of Asynch BR over After BR or vice versa.

3. Can we call scheduled job from BR?

4. Did you ever called script include in BR? Why we call script include in BR if we can write same script in BR itself?

Real Time Sample Questions:

1. How do you debug BR? What are the different ways to debug BR?

2. Explain any scenario where we can't use Asynch BR?

3. Explain any scenario where we can use Display BR instead of using GlideAjax?

Most candidates who fail weren't underskilled. They were underprepared.

Free questions cover the basics. The Job Switch Kit covers everything else.

500+ Q&A — Technical + Behavioral, structured by module
15-Day Structured Roadmap — Day-by-day plan that peaks on interview day
Unlimited Interview Bot — Practice live, every session recorded and reviewable
Salary Negotiation Playbook — Counter-offers, CTC decoding, in-hand strategy
Job Switch Strategy Guide — Notice period, BGV, resignation, offer comparison
Progress Tracker + Notes — Always know exactly what to tackle next
LinkedIn Profile Optimisation — Get found by recruiters before you even apply
Get Job Switch Kit →

🔒 Secure payment via Razorpay · Instant access after payment

10 days free — for your honest review

Your story could be the reason someone else lands their next ServiceNow role

If this content made a real difference in your prep, sharing that experience with your network helps other professionals discover it — and we'd love to say thank you with 10 days of premium access, completely on us.

Real Interview Questions & Answers

Questions shared by ServiceNow professionals and reviewed for clarity, relevance, and interview usefulness.

Sharique 27 Aug 2026
How can you implement the scenario where logged in user will only get to see the list of incidents in list view where the caller is the logged in user only.
No answers yet
0 helpful
*Please enter a reply
Harsh 03 Jun 2026
If you write a script to update a record inside a Business Rule, what is the architectural difference between calling gr.setWorkflow(false) versus gr.setForceUpdate(true)? Provide a real-world scenario for each.
No answers yet
0 helpful
*Please enter a reply
Sourav 31 Jul 2025
business rule to create a ctask under a change request when that change request is created via recorrd producer
No answers yet
0 helpful
*Please enter a reply
Harika 21 Dec 2024
Sir, I am confused about when to use before, after, async business rule? I know what they are and how they work but it seems like what can be done with before can also be done with after, so what's the point of them and next question is if in async business rule there is no current and previous then how we can access the current record while using async business rule? and where should we use trycatch
1 answer
Sudden_handle 27 Dec 2025
I had the same confusion when I first started learning Business Rules. The difference between Before, After, and Async becomes clearer when you think in terms of when the record is saved and what you are trying to update. I’ll explain this using simple scenarios so you can analyze and decide which type fits your use case. Before Business Rule A Before BR runs just before the record is written to the database. At this stage, the record is already prepared for saving, so you should not use current.update() here. Use a Before BR when you want to: Modify fields on the same record Inject or adjust values right before the save happens Examples: Automatically populate the Closed by field when the state is set to Closed, without requiring the user to fill it manually. (Example) If Priority = Critical, automatically update Urgency. In these cases, you’re simply setting additional field values on the current record that’s about to be saved. After Business Rule An After BR runs only after the record has been successfully saved to the database. This is important when your logic depends on the record actually being committed. Use an After BR when you need to: Update other tables Update related records Ensure all mandatory fields are satisfied and the save is successful Examples: When an Incident is Resolved, add a work note to the related Problem record. Although you could technically check current.state == 'Resolved' in a Before BR, if the record fails to save due to a missing mandatory field, the Problem record would still get updated. Using an After BR prevents this issue. When an Incident is Closed, automatically close all its child Incidents. If you use an After BR to update the same record, you would need to call current.update(), which is generally not recommended and should be avoided when a Before BR can do the job. Async Business Rule An Async BR runs after the transaction completes, at a later point in time, without making the user wait. Use Async BRs for: Background processing Actions that don’t require immediate user feedback Examples: Sending notification emails, Generating reports, Updating data that doesn’t depend on user interaction In Async BRs: The current object is available The previous object is not available This is because multiple updates may have already occurred by the time the Async BR executes, making the previous state unreliable. Display Business Rule A Display BR is typically used to pass server-side data to the client using the g_scratchpad object. This data can then be accessed in: Client Scripts, UI Policies, onChange and onSubmit Client Scripts Try/Catch Usage try/catch is standard JavaScript error handling and can be used in Business Rules when: You’re unsure if data exists, There’s a possibility of unexpected data or validation issues Using try/catch helps: Prevent script failures, Ensure smoother execution, Make debugging easier without breaking other scripts Please add anything if I misunderstood.
0 helpful
0 helpful
*Please enter a reply
Sonu 09 Sep 2024
What is the backend process in service catalog?
1 answer
Tarun Teja 26 Mar 2025
In ServiceNow, the backend process for the Service Catalog involves defining and managing catalog items, their workflows, and the fulfillment processes that occur when a user requests an item, including creating records, assigning tasks, and triggering approvals
0 helpful
0 helpful
*Please enter a reply
Keerthana Arumugam 21 May 2024
How to call business rules from scheduled job
1 answer
Anil 07 Jul 2024
you can write BR name in job context , use below syntax JOB CONTEXT: fcScriptName=Business_rule_name
0 helpful
0 helpful
*Please enter a reply
Lakshmi 20 Mar 2024
What is order of running the rules like which rule runs first business rules ,second Ui policy and so on
1 answer
Pradeep 03 Apr 2024
This is my understanding, Query BR -> Display BR -> On Load CS -> On Load UI Policy -> On Change CS -> UI Policy -> Before BR -> After BR -> Asycnh BR
0 helpful
1 helpful
*Please enter a reply
Ram 29 Jan 2024
how to call script include in business rules?
2 answers
Kushal Tm 02 Feb 2024
for example, write below code in your BR. var scrptInc=new yourScriptIncludeName(); scrptInc.functionNameOfYourScriptInclude();
1 helpful
Gvk 08 Sep 2025
method 2 : new scriptIncludeName().myFunction();
0 helpful
0 helpful
*Please enter a reply
Mounika 16 Nov 2023
how to call an event through business rule?
1 answer
Anonymous 17 Nov 2023
gs.eventQueue('event name',current,parm1,parm2);
2 helpful
0 helpful
*Please enter a reply
Supritha 15 Nov 2023
What is GlideRecordSecure? What is the difference between GlideRecord and GlideRecordSecure: Answer: GlideRecordSecure is a version of GlideRecord that provides an additional layer of security. GlideRecordSecure is designed to prevent unauthorized access to data. GlideRecordSecure enforces access controls and ensures that the user has permission to access the records they are querying. Developers can then use GlideRecordSecure in the same way as GlideRecord to query and manipulate ServiceNow records. GlideRecord queries and manipulates data in the same way as GlideRecordSecure, but GlideRecordSecure provides additional features for securing sensitive data. This ensures that sensitive data cannot be intercepted by unauthorized users as it enforces access controls. Another difference between the two is performance, Because GlideRecordSecure enforces access controls, it may take longer to execute queries than GlideRecord.
No answers yet
5 helpful
*Please enter a reply
Urmila Mukati 05 Nov 2023
Interviewer asked me why we use async BR to trigger notification instead of this we can also trigger notification by it's condition itself. Why we need BR can someone please answer?
1 answer
Venkat 10 Oct 2024
Business Rule: With an async Business Rule, you can implement complex logic and conditions that may be difficult or impossible to achieve using the standard notification condition builder. This gives you greater flexibility to decide when and how the notification should be triggered. Example: If the notification depends on a combination of factors or involves checking multiple related records, this can be handled in a Business Rule more easily than using notification conditions alone.
0 helpful
0 helpful
*Please enter a reply
Saidulu Yadav 25 Aug 2023
what is main difference between UI Policy and Client Scripts.
3 answers
William 06 Oct 2023
- We can execute client script on submit or on cell edit (list field update) but we cannot execute UI policy on submit or on cell edit. - We can execute client script for specific view but we cannot do the same via UI Policy. - UI Policies are faster as compare to Client scripts, therefore ServiceNow recommends to use UI Policies wherever possible.
0 helpful
Arpan 16 Oct 2023
UI Policies can be run for a specific view if you uncheck the Global field and then enter the view name you need.
1 helpful
Surendra 23 Oct 2023
Hi William We can execute client script or UI policy for the specific view as well.
0 helpful
2 helpful
*Please enter a reply
Ranjit 07 Aug 2023
Whether the g_scarthpad can be used on all the types of client script?
2 answers
Naveen 19 Aug 2023
g_scratchpad is used only in Onload Client scripts to get the data from Display business rule.
1 helpful
Roshan 24 Aug 2023
In most of the use cases, we access it in onLoad client script. However g_scratchpad object can be accessed in all type of client scripts. In fact it can be accessed in UI policy script also. Here is very important use case where it can be used in on submit client script, if we want to validate something on submit of the form but data is not available on client side. Normally we use GlideAjax to get server side data but GlideAjax fails in onSubmit client script (GlideAjax is asynchronous call therefore form gets submitted before GlideAjax returns result). Therefore we can store result in g_scratchpad object in onChange client script and based on value we can restrict form submission in on submit client script.
0 helpful
0 helpful
*Please enter a reply
Ann 07 Jun 2023
Hi How to autoclose REQ and RITM when task is closed.
1 answer
Saba Anjum 01 Jul 2023
to achieve this we can write two BR 1-sc_task 2- on table sc_req_item condition-state changes to closed complete logic 1- var rtm = new GlideRecord('sc_req_item'); rtm.addQuery('sys_id', current.request_item);//request_item is a field of sc_task rtm.query(); while (rtm.next()) { rtm.state = '3'; rtm.update(); } logic2-var req = new GlideRecord('sc_request'); req.addQuery('sys_id',current.request); req.query(); if(req.next()){ req.request_state = 'closed_complete'; req.update();
0 helpful
0 helpful
*Please enter a reply
Annin 09 May 2023
Hi I have asked a question when the incident state is closed related problem state should also be closed How can we do this
1 answer
Gaurav 10 May 2023
We can write After BR as below to achieve this requirement: Table : Incident BR Condition : When state changes to Closed var grProblem=new GlideRecord("problem"); if(grProblem.get(current.problem_id)){ grProblem.setValue("state",3);//3 is closed state back end value grProblem.update(); } Tip : Interviewer later asks why After BR, why not before BR or Asynch BR? short and simple answer is, if we are updating other than current record then we are supposed to use after BR. If script is too lengthy and execution time is high then we can go with Asynch BR (which runs in backend so that user don't have to wait till BR executes)
0 helpful
0 helpful
*Please enter a reply
Kiran 28 Apr 2023
How to trouble shoot if user is not able to login?
2 answers
Pratiksha 04 May 2023
There could be different reasons why user is not able to login but most common is wrong password or user doesn't exist in ServiceNow. Therefore, we can troubleshoot issue by following below steps 1. Verify if user exist in ServiceNow User(sys_user) table. 2. Try resetting user password.
0 helpful
Astik 09 Dec 2023
If user is not able to login please check below things 1.User is active 2.user id is not empty 3.Most Important - User is not locked out
1 helpful
0 helpful
*Please enter a reply
Anoynymous 17 Apr 2023
What if we have before query BR which is filtering data to show only active incidents. what will happen if we use the fix script on the incident(via glideRecord) will it show all the records in the present in the incident table if no addQuery is used?
1 answer
Anubhav 17 Apr 2023
If before query BR is adding filter to show only active incidents and if we try to GlideRecord on incident table then it will return only active incidents. Before query BR executes every time action is performed on database, it doesn't matter if database action is performed via UI or via script.
3 helpful
2 helpful
*Please enter a reply
Rishikesh 30 Mar 2023
Why current.update() in before BR doesn't create recursion call to same BR infinitely?
1 answer
Akanksha 30 Mar 2023
System has internal detectors for this and will prevent an endless series of such Business Rule executions, the detection of this has been known to cause performance issues in that instance. Source : https://support.servicenow.com/kb?id=kb_article_view
0 helpful
0 helpful
*Please enter a reply
Riddhi 29 Mar 2023
I was given a scenario where I said, I can use after BR to achieve it. But, he asked me why After BR? why not before or Asynch BR? I was not able to justify my answer. Can somebody explain what should be the proper answer to this question? this was asked two times to me for different scenario.
3 answers
Akanksha 30 Mar 2023
I think answer depends on given scenario. However, below are the short and simple use cases for different BR. Before BR : Use this BR when you want to update anything on current record. If you use After or Asycnh BR for such scenario then you will have to use current.update() which is not considered as best practice. Asynch BR : When you want to perform any operation which takes long time to execute. This way, user don't have to wait for this BR to complete as it runs in backend asynchronously. After BR : When you want to perform any operation on other than current record, it could be record in other table or same table but other than current record. Hope this helps.
0 helpful
Priyanka 23 Jul 2025
Before Business Rule: A Before BR runs before the record is saved to the database. It’s best for scenarios where I want to validate or modify data on the current record. However, it’s not ideal when I need to create related records or trigger flows, because the current record’s sys_id isn’t guaranteed to exist yet. Relying on it too early could cause data integrity issues or trigger failures. Async Business Rule: An Async BR executes after the record is committed, but runs in the background. It is faster in terms of not blocking the main transaction, so it’s useful for non-critical operations like logging, notifications, or calling external systems. But for flows and catalog requests that require sequential execution or guaranteed timing, async rules can introduce risks, since they have no guaranteed execution time or order. It may delay or fail silently, which is unacceptable for time-sensitive tasks. After Business Rule: An After BR runs immediately after the record is saved and within the same transaction. This makes it ideal for creating dependent records, updating related tables, or triggering flows that rely on data that is now committed, including the sys_id. It ensures that everything runs in a reliable sequence and within a guaranteed time frame. In catalog requests or flow orchestration, this level of control is critical, so After BR becomes the best fit.
1 helpful
Gvk 05 Mar 2026
the `current.update()` method is used to explicitly save changes to a record. This method is particularly relevant in certain types of Business Rules (BRs) where updating the record is necessary or appropriate. 1. Before Business Rules: - Usage of `current.update()`: Not recommended. - Reason: Before Business Rules run before the database operation (insert, update, delete) occurs. Using `current.update()` here can cause recursion issues because the rule itself is triggered by a record operation. Since Before Business Rules are designed to modify the record before it's written to the database, the platform will save changes to the record automatically after the Before Business Rule completes. Using `current.update()` here can lead to infinite loops or unexpected behavior. 2. After Business Rules: - Usage of `current.update()`: Can be used. - Reason: After Business Rules execute after the database operation has completed. These rules are ideal for situations where you need to perform additional actions based on the changes made to a record, and then save these further modifications. Since the primary operation has already been completed, using `current.update()` here to make further changes won't cause the same recursion problems as in Before Business Rules. 3. Asynchronous Business Rules (Async BRs): - Usage of `current.update()`: Can be used. - Reason: Async BRs run in the background after the database operation has completed. They are used for tasks that don't need to be completed immediately and won't hold up the user interaction. `current.update()` is safe to use here to make further updates to the record, as it won’t affect the performance of the user-facing operations. 4. Display Business Rules: - Usage of `current.update()`: Not applicable. - Reason: Display Business Rules execute when a form is loaded and are used to manipulate the data before it is presented to the user. These rules are read-only and are intended to prepare data for display purposes. Thus, using `current.update()` within Display BRs is not relevant, as these rules should not modify the record.
0 helpful
0 helpful
*Please enter a reply
Share a Question
?
Questions are reviewed before publishing to maintain quality. Include the role, scenario, or context if possible — specific questions are more useful to others.
* Please enter a question before submitting.

🚀 Power Up Your ServiceNow Career

Join a growing community of smart ServiceNow professionals to stay ahead in interviews, sharpen your development skills, and accelerate your career.

📱

ServiceNow Buddy App

Get the free Android app for a smoother experience.

Install
Comments 1
R
Rahul 16 Oct 2024
Sir, I am confused about when to use before, after, async business rule? I know what they are and how they work but it seems like what can be done with before can also be done with after, so what's the point of them and next question is if in async business rule there is no current and previous then how we can access the current record while using async business rule? and where should we use trycatch
* Please enter a comment before submitting.
📝 My Topic Notes 🔒 Only visible to you
Previous Client Script Questions Next Scenario Based Questions

Found these questions helpful?

Share your experience — it helps other ServiceNow professionals know what to prepare.

Share Your Story →