How do I avoid using current.update() in a business rule script by using setWorkflow() method with the false parameter

zag
Tera Expert

This script was developed to add users to the watchlist for every case if a Watchlist = True check box is active in their user profile. However this business rule is causing some recursive issues.  Based on the feedback from SN I need to stop using current.update and start using the setWorkflow(false) method.   Can someone help me modify the code below appropriately. 

This is the feedback from ServiceNow 

First and foremost, Its not recommended to use current.update() in "After" Business rule. 
Because it will lead to recursive call. It is documented here : 
-https://docs.servicenow.com/bundle/kingston-application-development/page/script/business-rules/reference/r_HowBusinessRulesWork.html#d746702e265 

"Avoid using current.update() in a business rule script. The update() method triggers business rules to run on the same table for insert and update operations, leading to a business rule calling itself over and over. Changes made in before business rules are automatically saved when all before business rules are complete, and after business rules are best used for updating related, not current, objects. When a recursive business rule is detected, the system stops it and logs the error in the system log. However, current.update() causes system performance issues and is never necessary. 

You can prevent recursive business rules by using the setWorkflow() method with the false parameter. The combination of the update() and setWorkflow() methods is only recommended in special circumstances where the normal before and after guidelines mentioned above do not meet your requirements." 

In this business rule "Set watch_list acc to addtocasewatchlist" I see you are doing current.update() as many times as that of people in the watchlist. 
This is causing the case record to get updated as many times at the same time frame. 

 

 

When to Run:   When = After  , and Insert = True

Advanced

(function executeRule(current, previous /*null when async*/) {

// Add your code here
// var watchlist = [];
// watchlist = current.watch_list.split(',');
var str1 = current.watch_list;
var gr = new GlideRecord("sys_user");

gr.addQuery("company",current.account);
gr.addQuery("u_add_to_case_watchlist",true);
gr.query();
while (gr.next()) {
var str2 = gr.sys_id;
if(!current.watch_list)
{
current.watch_list = gr.sys_id;
}
else if(str1.indexOf(str2) == -1)
{
current.watch_list = current.watch_list +','+ gr.sys_id;
}
current.update();

}

})(current, previous);

 

 

18 REPLIES 18

Even if you handle this from an event if you use current.update() in script action. it will retrigger the BR and causes recursion.

At that point it would be an update and will not fire the BR.

Please mark Correct and click the Thumb up if my answer helps you resolve your issue. Thanks!
Vinod Kumar Kachineni
Community Rising Star 2022

It will trigger because we are updating the same record, (As BR is configured to run on insert and update (after)) - based on  scenario of the original question

Did not realize it is for both insert and update. May be I missed the update part in the thread.

 

find_real_file.png

Please mark Correct and click the Thumb up if my answer helps you resolve your issue. Thanks!
Vinod Kumar Kachineni
Community Rising Star 2022

oh sorry.. Im thinking that it is configured for both insert and update.

 

But Im confused now :

 

how current.update() is causing recursion in the above BR which is configured to run only on insert??