When upgrading from any prior version to Fuji or later, a version 2 Knowledge Base is created, and existing knowledge is moved to it. ACLs for v2 Knowledge apply to this Knowledge Base to determine read/write/create access, while User Criteria is used to determine access to v3 Knowledge Bases. OOB, the platform hides the User Criteria related lists Can Contribute and Can Read on v2 Knowledge Bases so that users cannot add User Criteria without customization. Because no User Criteria is on v2 Knowledge Bases, the Create Content button displays on the Knowledge landing pages.

Steps to Reproduce

  1. Log in to an instance that has been upgraded to any version of Fuji.

  2. ACLs for v2 are set to restrict create/write to kb_knowledge and are set to Knowledge Role.

  3. User Criteria for v3 Knowledge Bases are set to Users with Knowledge Role.

  4. Log in as an ITIL user.

  5. Navigate to Self-Service > Knowledge.

    Note that the Create Content button is visible even though ITIL users do not have ACL or User Criteria access to create / write content.



Add User Criteria to v2 Knowledge Bases.

  1. Deactivate the "Hide V3 related lists on knowledge base" client script so that the Can Contribute / Can Read related lists are visible on v2 Knowledge Bases.

  2. Modify the condition on the Edit UI Action for the kb_uc_can_contribute_mtom table by removing "(parent.kb_version !=2)" from the condition to allow the Edit button to appear on the Can Contribute related list in the v2 Knowledge Base.

  3. Add User Criteria to the v2 Knowledge Base.

Note – Another possible but not recommended workaround is to modify the KBKnowledgeSNC UI Script to ignore v2 Knowledge Bases.



Related Problem: PRB648252

Seen In

Fuji Patch 12 Hot Fix 1
Fuji Patch 7 Hot Fix 5

Fixed In

Fuji Patch 12
Geneva Patch 4

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-08-17 07:03:05