Async business rule deprecated

Indira8
Kilo Sage

Hi All,

 

We have recently upgraded our customer instance from Qubec to Sandiego version and as result of the upgrade following changes are found:

1. Business Rules when to run "async" condition deprecated.  We have 80 BRs in total with the deprecated value, I have read the KB article 'https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951770' however did not understand whether we have to change the choice from old async to the new async. 

Is there any action required as a developer.

Thank you 

1 ACCEPTED SOLUTION

MrMuhammad
Giga Sage

Hi @Indira,

Let me try to explain this in simple words.

Basically, the old async BR runs fairly soon after the record action (insertion, update etc) has happened without locking the screen for the user's to use. however, when an instance upgrade is in progress this BR doesn't trigger until the upgrade is completed so e.g. you have an integration in place to sync incident tickets between multiple instances so while the instance is upgrading any incident created might not flow to other instance because async BR is blocked.

With the introduction to the new async BR you won't be facing the above issue during the upgrades. Even while the upgrade is in progress your BR will trigger and perform the necessary action.  

Reference: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951770

Hope that helps!

Please mark this helpful/Correct, if applicable.

Regards,

Muhammad

Regards,
Muhammad

View solution in original post

5 REPLIES 5

Shubham Tipnis
Kilo Sage
Kilo Sage

Hi Indira,

I think this deprecation has been done in Rome itself. Found this discussion thread. Check if it helps you. Its better to do a round of testing on some existing scenarios where your async BR's are triggered. This will help you assess if you need to do any changes.

Please mark correct/helpful if applicable.

Regards,

Shubham

 

Regards,
Shubham Tipnis
 ServiceNow Enthusiast
️ 3x Rising Star (2022–2024) – ServiceNow Community
 Sharing insights, use cases & real-world learnings from the Now Platform
 Always learning. Always building.

hi @Shubham Tipnis , thank you for the thread but that was also a bit confusing so I posted a new question. We have to answer our client whether we need to update all our BRs to the new async choice value

Thank you 

MrMuhammad
Giga Sage

Hi @Indira,

Let me try to explain this in simple words.

Basically, the old async BR runs fairly soon after the record action (insertion, update etc) has happened without locking the screen for the user's to use. however, when an instance upgrade is in progress this BR doesn't trigger until the upgrade is completed so e.g. you have an integration in place to sync incident tickets between multiple instances so while the instance is upgrading any incident created might not flow to other instance because async BR is blocked.

With the introduction to the new async BR you won't be facing the above issue during the upgrades. Even while the upgrade is in progress your BR will trigger and perform the necessary action.  

Reference: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951770

Hope that helps!

Please mark this helpful/Correct, if applicable.

Regards,

Muhammad

Regards,
Muhammad

hi @Muhammad thank you for the detailed way of explaining. 

It helped me understand the difference.