Hi @VullankiL
Use a "Flag" Field and a Before Business Rule:
This is often the recommended approach when dealing with cross-scope issues and wanting to prevent other business rules from executing.
Add a Flag Field: Add a custom field (e.g., u_skip_br_processing, type: true/false) to the asmt_assessment_instance table in the Global scope.
Set the Flag: In your current business rule (in the "EITG" scope), instead of calling setWorkflow(false) directly, set this new flag field to true on the asmt_assessment_instance record.
Create a Before Business Rule in Global: Create a new "before" business rule on the asmt_assessment_instance table (in the Global scope) with a high order value (e.g., 50). This rule should have the following logic:Condition: current.u_skip_br_processing == true
// Business Rule: After - Update on [Your Table]
// Scope: x_weoi2_eitg_confi (or EITG)
// Order: 1000 (or higher)
(function executeRule(current, previous /*null when async*/) {
var gr = new GlideRecord('asmt_assessment_instance');
gr.addQuery('related_id_1', current.related_id_1);
gr.addEncodedQuery('state!=complete^ORstate=NULL');
gr.query();
while (gr.next()) {
gr.setValue('state', 'canceled');
// Set the flag field to prevent other business rules from running
gr.u_skip_further_br = true;
//Update the record
gr.update();
}
})(current, previous);
If you like this opinion and your problem is resolved after reviewing and applying it. Please kindly mark this your best answer🌠 OR mark it Helpful ⛑ if you think that you get some insight from this content relevant to your problem and help me to contribute more to this community
MackI | ServiceNow Technical Consultant | DXC Technology Australia | ServiceNow Practice | LinkedIn Top IT Operation Voice 2023 | Sydney,Australia
