The UI Actions in the knowledge articles are not visible for usersDescription<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms The checkout, publish, Retire UI actions are not visible Release Kingston Patch 11 Cause The issue is caused due to the v3 knowledge base UI action conditions being evaluated to the v2 knowledge base Resolution The issue is caused due to the v3 knowledge base UI action conditions being evaluated to the v2 knowledge base. The issue occurs when the instance has both v2 and v3 knowledge bases enabled. It is recommended that all the knowledge bases are migrated to v3. For temporary relief, please follow the steps below: In the Review UI action (for instance) 1. The UI action condition is failing at this function call " new KBKnowledge().canRetire(current)" 2. In the KBKnowledgeSNC (base class which is extended in the child KBKnowledge) script include, the function "canRetire" is, in turn, calling another function named "canRetire" in the script include, KBVersioning 3. The function is defined in the base class (base script include KBVersioningSNC) 4. Therefore that function can be overridden by defining our own custom function (that skips the canContribute condition check for v2 knowledge bases but still checks the condition for v3 knowledge bases) in the Child script include "KBVersioning". 5. To do this copy the entire "canRetire" function from the base class and paste in the child class. Have an if condition that checks if the knowledge base is v2, then add your own condition that determines who should see the UI action. The same steps can be followed for Publish and Checkout UI actions.