What is the Purpose of write ACL for closed_by in problem, for users with role nobody

[Rohitha15]

Hi,

I have written 2 scripts to update the 'closed_by' field with the value in 'resolved_by' field in both the problem and incident tables [For Auto Closure].'closed_by' field is updating with 'resolved_by' in incident table but it is not updating in the problem table.

While debugging, I observed that there is a high priority write ACL on problem field "closed_by" for the users with nobody role. I feel it is blocking the update.

Can anyone mention the purpose of that ACL? Attaching the screenshot for the reference.

Many thanks in advance,

Rohitha.

[Kieran Anson]

Could you share your scripts? If a script is running service side and using GlideRecord, it won't be subject to the restrictions of an ACL - ACLs only apply to a users interaction. The intention of this ACL is to prevent anyone from writing to that field via the UI/an API call. 

[Rohitha15]

I am triggering a business rule from sys_trigger table that will run daily at specified time. I am using GlideRecord to query the resolved problem and closing it if they are resolved before mentioned days.

As you said If a script is running service side and using GlideRecord, it won't be subject to the restrictions of an ACL.I believe it is not blocking my update.

Thank you.

[Runjay Patel]

Hi @Rohitha15 ,

No, OOB ACL not blocking you to update the problem. Share your code which you are trying to run to update the problem.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------