Restrict Low-Priority Incident Creation via Point of Entry Field in Emergency Change

nandini29
Tera Expert

Hi All,

In the Emergency Change form, there is a field called Point of Entry, which is intended to accept high-priority incidents only. Normally, this field does not accept low-priority incidents. The lookup list for this field displays only high-priority incidents; however, when users use the New button from the lookup list, they are able to create low-priority incidents. Consequently, the Point of Entry field ends up accepting low-priority incidents through this method.

We need a way to restrict the creation or selection of low-priority incidents from the lookup list so that the field enforces its high-priority restriction consistently.

nandini29_1-1766064042731.png

 Can some please suggest what will be the best solution for this?

 

14 REPLIES 14

Anand2799
Tera Guru

Hi @nandini29 ,

 

Follow below steps:

Open incident list -> Configure -> List Control

Omit New Condition

Add script: (Add your correct table name and field)

answer = false;
if (RP.getParameterValue('sysparm_target') == "incident.caller_id") { // update this to your table name and field name
    answer = true;
}
answer;

 

Thanks

Anand

Me Being Mustaq
Tera Guru

Hi @nandini29 ,

 

To enforce consistent high-priority filtering in the Point of Entry field of your Emergency Change form—even when users click the New button from the lookup list you can implement a combination of UI policy, dictionary-level constraints, and form-level scripting.

 

  • Log violations or attempts to select low-priority incidents.
  • Notify users with a clear message explaining the restriction.

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

 

Kind Regards,

Shaik Mohammed Mustaq

 

Ankur Bawiskar
Tera Patron
Tera Patron

@nandini29 

Would you mind closing your earlier questions by marking appropriate response as correct?

Members have invested their time and efforts in helping you.

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

Accepted it, Thanks for the solution