The CreatorCon Call for Content is officially open! Get started here.

New ServiceNow Security ACL Updates

Zackery Reynold
Mega Sage

There was an update in ServiceNow where they added 23k new ACLs in our instance for query_range.

 

I noticed when they update a table, they don't update all the fields and it broke our reports.

 

For example, our Group table's ACLs were updated and it added one for the Manager field in the group's hierarchy, but it didn't update the other fields in the hierarchy like escalation points, etc. The reports would show a user having 35 active tasks in their group's list, but when they click in it shows 5 and has an error for the query_range.

 

We fixed it by creating a query_range for those 5 fields that were missing.

 

I wanted to ask the community if they've noticed anything that affected their instance that we should be aware of?

 

We're currently figuring out how we can test to see if anything else is broken before a user notices it, and figured this would be a good start.

 

 

4 REPLIES 4

Chaitanya ILCR
Mega Patron

Hi @Zackery Reynold 

 

yes, this happened with so many other customer instances too including ours

 

refer this KB

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2046494

 

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

Was there anything you noticed that affected your instances that you had to manually adjust or create a new ACL so it functioned before the update was made?

Yes some customer are facing issue in the service portals

we didn't get any incidents in our instance but our team is planning check with servicenow and backout those changes

 

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

anand-bhosle
Tera Guru

Hi @Zackery Reynold @Chaitanya ILCR 

 

We recently seen this issue happening with our Vendor portal [/svdp] where users were unable to see questionnaire. We noticed there are updates to service portal widget update where instead of using GlideRecord servicenow introduced GlideRecordSecure which caused the issue. Reverting them back to GlideRecord fixed our issue with query_range ACL.

 

Start looking in that are if you still facing the issue. 

 

Thanks

Anand