Reassignment counter increased by 2 for single change in assignment group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
In my ServiceNow instance Reassignment counter is getting increased by 2 for single change of assignment group. This is an intermittent issue. As per ServiceNow support this is occurring due to custom "Save" button on form. Following is the condition and script for the "Save" button. Can someone help me to understand what is in the script that is causing the issue
Condition : !(current.isNewRecord() && !current.canCreate()) && current.canWrite()
Script:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Ankur Bawiskar
I got the root cause for the issue, the following after BR runs on insert and update when assignment group field updated with particular assignment group on sc_task table.
The update statement in this BR(current.update() ) triggers the BR for reassignment count increment again. Is there way to avoid this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
use setWorkflow(false)
current.correlation_display = taskcorrelationDisplay;
current.setWorkflow(false); // avoids triggering any other BR
current.update();
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
is your UI action's "Action name" the same name as another UI action available to the table? try renaming the custom UI Actions "Action name" and see if it still saves 2x.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
@Jeffrey Siegel
I did check but there is no other UI action present with same name on that table
