Enforce mandatory fields in Service Operations Workspace (SOW) list view

m_osborne
Kilo Sage

 

We recently realized that the mandatory field enforcement that we see in the list view on the platform of ServiceNow is not reflected in the Service Operations Workspace (SOW) list view.

 

Mandatory field enforced in list view on platform:

m_osborne_0-1724071355431.png

 

Mandatory field not enforced in list view in SOW:

m_osborne_1-1724071605967.png

m_osborne_2-1724071829361.png

 

I have seen other forum posts mentioning to use Data Policies to enforce this in SOW, which I did implement. In certain scenarios, however, this method cannot be used. Data Policies cannot be used to enforce mandatory fields on new Interactions as this would prevent Interactions from being created using Agent Chat in the Service Portal. In addition, Data Policies cannot be used to enforce mandatory fields on new Incidents as this would prevent Record Producers from being submitted.

 

I am reaching out to hopefully see if anyone else had come across this issue and was able to figure out a way to enforce all mandatory fields in the SOW list view while not impacting those aforementioned scenarios.

 

As a last ditch effort to prevent the clearing of mandatory fields in the list view we are considering removing the ability to edit these fields from the list view, but would rather not as this would increase the work effort of our Help Desk.

 

Any help would be greatly appreciated!

1 REPLY 1

Nikolett Vincze
Tera Contributor

Hi,
we are facing the same issue.. The field is set to mandatory in the dictionary, but can be cleared out in the List in SOW...
Do you have maybe an update on this issue?

Thank you in advance