How to Keep "Any User" user criteria from adding back to Can Read
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2025 12:23 PM
Whenever I try to add a User Criteria to the "Can Read" related list in a Knowledge Base and remove the OOB "Any User," the "Any User" user criteria does not delete. Does anyone know if there is an OOB business rule, UI Policy, data policy, client script, or ACL that is causing this behavior??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2025 12:38 PM
Hi @BrownBear
I tried it on my end in the PDI, and I was able to remove it from the KB, and it didn’t get added back. Try repairing the Knowledge plugin and clearing the cache. If the issue persists, please log a Now Support case.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 11:41 AM
The part I left out of my original post is that there is no Application scope defined. On your PDI, try it on a KB that does not have an Application scope defined. Try adding a user criteria, remove "Any User", hit Save, then check if Any User is actually removed from the Can Read list of UC's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 11:55 AM
Yes, you are right, I created a new KB and I saw any user criteria is coming and when I try to remove and save, it added back. Looks like it is a bug here.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 12:11 PM
Oh good, I'm glad you experienced the same. This seems to only be an issue with KBs without a defined Application scope. This doesn't seem to affect KBs that have a defined Application scope. I agree that this is either a bug with KBs with undefined Application scopes or there is an OOB Business Rule, UI Policy, Client Script, or ACL that I have yet to find that contains a trigger that does not allow the "Can Read" related list to ever be empty.
If someone knows otherwise, please share.
