"can read" and "cannot read" related lists on KB articles

jayesh_hoondlan · ‎06-28-2017

how to setup "canRead" and "cannotRead" related lists on knowledge article in Istanbul, there is no OOTB related list for knowledge articles, thought present for knowledge base.

Chuck Tomasi · ‎06-28-2017

Hi Jayesh,

Thank you for sharing. I did not know about those fields. Very interesting.

To answer your question, the answer is no. Fields are fields, they appear on the form. Related lists are records in other tables that refer to the current record (either directly or via a many-to-many table.) They are two different things. Even if you were to create a related list with Can Read/Cannot Read and add User Criteria records, the logic isn't there in the platform to recognize and apply it to the current KB.

Can you help me understand what the motivation or value would be of having a related list of user criteria rather than list field on the KB?

Section 3.4 in this article may be helpful for understanding where the glide list fields and related lists are applied best.

http://wiki.servicenow.com/index.php?title=Modifying_the_Application_Design#Choose_the_Correct_Field...

View solution in original post

quoccsc · ‎05-02-2018

In Jakarta release, there are two fields at Knowledge Article level that references User Criteria:

+ can_read_user_criteria (Can Read)

+ cannot_read_user_criteria (Cannot Read)

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/product/knowledge-management/task/t_SelectUCArticle.html

Some override rules are applied and in general this addition gave user more control over access to individual knowledge article.

William Busby · ‎05-02-2018

The 'Can Read' and 'Can Not Read' do not work on individual articles in Jakarta. We'd hoped to leverage it and discovered it's only enforced for access to a knowledge base. We had to implement a 'before query' to employ article level restrictions.