Hi Guys,
---I have added an extra option for impact and urgency (1-Critical), the mapping was adjusted in the dl_u_priority table with a custom matrix.
---Till here it is fine, Now I have to revert the changes and bring it to original mapping, So I have de-activated the newly created choices in impact, urgency and priority look up table also.
--when I have done above changes, I am finding the below issue.
Any work-around available for above.
The data lookup definitions have a "Run on Update" option. You could run a background script on incident table and update all the incidents once, it should reset the Priority based on the look up matrix.
Before running the script on whole table, I would suggest testing the script with few records to avoid errors.
var gr = new GlideRecord('incident');
gr.addEncodedQuery("priority=1"); //copy your query from the table filter and paste here.
//gr.setlimit(3);
gr.query();
while(gr.next())
{
gr.update();
}
If my reply helped with your issue please mark helpful 👍 and correct if your issue is now resolved. ✅
By doing so you help other community members find resolved questions which may relate to an issue they're having.
Thanks,
Debopriya
