Identify What Controls Read-Only Setting on a Field

[Dan13]

I am trying to identify what is making the "Requested for" field read-only on the SCTASK form. I've gone through all of the configurations for tasks tabs and can't seem to find what is setting that field to read-only.

Does anyone know if there is another place that can control that field or maybe there is a log/history that tells me what is acting on that field?

[AshishKM]

yes, this message reflect that some ACL applied.

you can also check the ACL on request item table, because requested coming from request item table.

[AshishKM]

did you get the desire result. 

[Dan13]

Thanks. I got more info, but I'm not sure exactly what to do. I was comparing my dev instance to a PDI.

In my Dev instance:

Using field watcher, I can see the requested item ACL's run against the requested for field.

But, if I use the Debugger (as Maik linked below) and run it while opening the SCTASK, I get an ACL running on the catalog task table

I moved to the RITM level and found two ACL's that are running on the Requested for field

I tried turning off the sc_task ACL's and the sc_req_item ACL's with no change to the Requested for field.

In my PDI instance:

I get two ACL's running on the catalog task table

But I don't get anything using field watcher

[Maik Skoddow]

Hi @Dan13 

there is a helpful KB article regarding that topic which provides all places that have to be checked for getting an answer: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0783470

Maik