question when the task changes to next assignment group RITM needs to update with current task assignment .Bu in Community Central forum

when the task changes to next assignment group RITM needs to update with current task assignment .Bu

RevanthKumar200 — Tue, 02 Jun 2026 09:11:23 GMT

when the task changes to next assignment group RITM needs to update with current task assignment group.This is not configured in flow and this is working in Production but not in DEV,Test.so what is the solution how to know which triggers BR or anything in PROD and why its not working in other envireonments

Re: when the task changes to next assignment group RITM needs to update with current task assignment

Naveen20 — Tue, 02 Jun 2026 17:09:37 GMT

The behavior is driven by a Business Rule on the sc_task table (after/async update, when assignment_group changes) that writes back to the parent sc_req_item. Since it works in Production but not in lower environments, the BR almost certainly was not cloned/migrated to DEV/Test.

To identify what's triggering it in Production:

1. Go to Business Rules, filter table = sc_task, and search for rules referencing request_item or sc_req_item — look for one updating assignment_group.

2. Alternatively, enable the Script Debugger or check System Log → All while reproducing the task assignment group change in Production.

3. Compare the BR list between Production and DEV — the missing rule is your culprit.

To fix DEV/Test, export the Business Rule from Production via an Update Set and import it into the lower environments. The typical BR script looks like:

// sc_task | After Update | assignment_group changes

var ritm = new GlideRecord('sc_req_item');

if (ritm.get(current.request_item)) {

ritm.assignment_group = current.assignment_group;

ritm.update();

}

The root cause may be a missing Update Set promotion — the customization exists only in Production.

Re: when the task changes to next assignment group RITM needs to update with current task assignment

ashleyharve — Thu, 04 Jun 2026 14:08:15 GMT

Naveen20's diagnosis is spot on. Missing Update Set promotion is the classic reason a Business Rule works in Production but not in lower environments. The fix is straightforward: export the BR from Production as an Update Set, import it into DEV and Test, and preview before committing. For businesses using ServiceNow to manage customer service workflows where inbound calls are part of the process, Phonexa integrates call tracking data alongside ticketing systems to give a complete picture of customer interactions.