No Application Scope (sys_scope) on System Generated Fields (Defect?)

[Ben Vargas]

I have created a number of new tables in scoped applications that are not extended off of any Global table such as task and it doesn't appear that the Application (sys_scope) is being set on the system generated fields such as sys_created_on and sys_created_by. Is this a defect that ServiceNow is aware of?

This results in the Read Only property being greyed out when attempting to edit the dictionary, further troublesome is the UI Policy Action form does not allow the system fields to be selected to make them read only through that approach either. I suspect that I'll be able to use a Client Script to force sys_created_on and sys_created_by on the form to be read only, but this seems to be a defect in my opinion.

Has anyone else experienced this and/or is it a known defect ServiceNow?

[mbhmbhmbh]

I was trying to find information on the problem mentioned above, PRB1007487, but it does not exist when searching in HI. Can anyone point me in the right direction?

[denis hoffmann]

Hi,

you can find the HI answer here :
System Generated Fields have no Application Scope (sys_scope) value assigned and are not editable - KB0712986

Regards,
Denis.

[Ben Vargas]

In the end, ServiceNow decided this is not a defect and advised to use alternate methods to make system fields on custom tables read only or mandatory (dictionary method not supported on system fields inscoped applications).