After and Asynch BR

[Priyanka_Ghosh]

Can anyone give real-time use case with brief explanation where we can only go for "After" BR and not "Asynch" BR. Asynch BR just can be used in that scenario.

P.S: I'm just trying to understand the difference between the two BRs with example.

-Thanks

[Harish Bainsla]

Hi @Priyanka_Ghosh 

After business rules will execute after a record is saved/submitted/updated and after a database operation is performed. Async business rules work in a similar way to After, however Async rules will execute asynchronously (hence the name) meaning that they will not run immediately after the record is submitted.

for more details check below link

https://www.servicenow.com/community/itsm-forum/what-is-difference-between-after-and-async-business-....

https://youtu.be/pk6KWJm6U6Y?si=nOonxIrUbF1tMgrV

if my answer helps mark helpful and accept solution

[Saaniya Chugh]

Key Difference:

• "After" BR: Runs immediately after the record is saved and is used for tasks that require instant action or feedback.

• "Asynch" BR: Runs in the background after the record is saved, suitable for non-critical tasks that can afford a delay.

To understand the difference between "After" and "Asynchronous (Asynch)" Business Rules (BRs) in ServiceNow, let's use a relatable analogy and a real-world example.

Analogy:Imagine you are a manager in a busy restaurant.

• "After" BR: You check the orders after the chef has prepared them to ensure everything is correct before serving them to customers.
• "Asynch" BR: You let the chef prepare the orders, but you only check them later, after they’ve already been served, to record or update something that doesn’t immediately affect the customer’s experience.

Real-Time Use Case:Updating a Ticket and Sending a Notification.

• Use "After" BR:
  When a ticket is updated, you need to send an immediate notification to the assigned user.

  • Example: A high-priority incident is assigned to a user, and they must be notified immediately.
  • Why "After" BR? The notification must happen after the record is saved and the changes are committed to the database, but it cannot wait or run in the background because the user needs to act on it immediately.
    
    

• Use "Asynch" BR:
  When a ticket is updated, you want to log some audit data or update related records, but this action doesn’t need to happen immediately and can run in the background.

  • Example: A report logs how many high-priority incidents are assigned to a particular user.
  • Why "Asynch" BR? Logging audit data doesn’t affect the immediate functionality, so it can run in the background without delaying the user.

In short, go for "After" BR when you need real-time, immediate actions, and "Asynch" BR when the task can be delayed without impacting the user experience.

[Sandeep Rajput]

@Priyanka_Ghosh 

Here are some examples using which you can distinguish when to use "After" and "Asynch" BR.

After: Use after business rule when you want to make some changes on the instance itself after completing a database transaction(Insert/Update/Delete). For e.g. Create a problem record in the problem table whenever an incident on the incident table is created.

Async: Use Async business rule whenever you would like to perform an operation which is either time consuming or outside the perimeter of the instance. For e.g. you would like to make an API call to share the detail of recently created incident with a third party server or make an API to get details from a different server. Since you are not sure when you are going to get the response, an async business rule would be more appropriate to use in this case.