Employee Center Incident Record Producer showing P5 even after updating Priority Data Lookup

21121A1597
Tera Contributor

I am facing an issue with the OOB/Create Incident record producer in Employee Center.

Current behavior:

  • Impact = None
  • Urgency = None
  • Priority automatically displays P5 - Very Low on the portal form before submission.
  • After submission, the incident is created with Priority = P5.

Troubleshooting already performed:

  1. Updated all Incident Priority Data Lookup records that previously mapped to P5, changing them to P4.
  2. Verified that creating an Incident directly from the backend now results in P4 as expected.
  3. Reviewed the Record Producer script and found no explicit assignment such as current.priority = 5.
  4. Checked for Catalog Client Scripts and could not find any script setting the Priority.
  5. The Priority field on the portal is read-only and already shows P5 before the record is submitted.

Issue:

  • Backend incidents respect the updated Priority Lookup configuration.
  • Incidents created through Employee Center still default to P5.
  • I am trying to identify where Employee Center is deriving the P5 value from.

Questions:

  1. Is there a Script Include, Data Lookup Definition, Portal Widget, UI Policy, or another OOB component that calculates and displays the Priority before submission?
  2. Has anyone encountered a situation where backend incidents use the updated Priority Lookup matrix, but Employee Center continues to display and create incidents with P5 with impact and urgency as none.

Any guidance on where to trace the issue would be appreciated.

Thank you.

21121A1597_0-1792661891373.png

 

1 ACCEPTED SOLUTION

So I've set my Impact and Urgency to have a None, like yours, and removed the default values and I get the same as you (Priority = P5). 

I've done some further looking and Incident has a Dictionary Override for Task, which sets the Default value to 5. You can find this here: /nav_to.do?uri=sys_dictionary_override.do?sys_id=31003e229f2112008f97b89a442e7009

 

After changing this override to 4, I now get 4 - Low as my default priority (as shown below).

Kieran3_0-1792669415235.png


If this solves your issue, please be sure to mark it as the correct answer to help others find it 🙂

View solution in original post

8 REPLIES 8

Kieran3
Mega Sage

Hey @21121A1597, it sounds like you're trying to directly set the Priority field. In your screenshot, you have Impact and Urgency empty. Priority is determined by setting the Impact and Urgency fields which then calculates priority.

21121A1597_0-1792663415099.png

IF i create incident from employee center portal which record producer the incident is created with priority as p5 default without any impact or urgency thats the issue

So the OOB 'Create Incident' record producer only asks for Urgency. 

Kieran3_0-1792665071103.png

You need users to provide Urgency and Impact if you want a priority to be determined. You don't need Priority on the record producer - and probably shouldn't as some users could up the Urgent/Impact value to give a higher Priority in hopes it will be resolved quicker.

We have customed the record producer and we dont use any variables like impact urgency or priority directly just few variables like affected user , mobile no, description and short description but don't know how it is setting to p5 without impact and urgency i could not find any BRor any catalog client scripts