Add Ownership Group field to New Knowledge Form

Tasha3 · ‎05-09-2023

I enabled Ownership Groups by setting glide.knowman.ownership_group.enabled to true; I also created one new Ownership Group to try this out. However, how do I add a field for "Ownership Group" to our Create New Knowledge form? My understanding is that there needs to be a dropdown for "Ownership Group" when someone creates an article. Then the author can select the appropriate group that their respective article belongs to. Or am I understanding this incorrectly? If that's right, how do I get that field to appear?

Tasha3 · ‎05-12-2023

Turns out the solution is simpler than I anticipated, but it took a while to figure this out! I needed to go into a new article, click on the Hamburger menu > Configure > Form Layout > then move Ownership Group over into the available fields. I myself can only do this in our Test instance where I the correct role, which I think is personalize_form.

View solution in original post

Dave Littlejohn · ‎05-09-2023

It should automatically have that on the new knowledge article record. if not, check to see if the client script "OwnershipGroup:hide ownership groupfield" is enabled.

Tasha3 · ‎05-09-2023

Thanks, I searched for "OwnershipGroup:hide ownership groupfield" which led me to a Catalog UI Policy with a Catalog UI Policy Action of ownership_group, which we had set to "false." I was hopeful that changing that to "true" would do the trick, but I'm still not seeing the field. I'll keep digging.

Dave Littlejohn · ‎05-09-2023

Looking at that screenshot, I believe you are setting a catalog variable for the Catalog Item "Manage Knowledge Ownership" to be visible. This wouldn't have any effect on the knowledge article records.

Do you know if you have Knowledge Management Advanced plugin activated? If so, you may need to repair/reinstall it.

Tasha3 · ‎05-09-2023

Interesting thought regarding the plug-in. I assume we have it on because we have article versioning turned on, which I think also needs that plugin? But I will reach out to our developers to check — it may need to be repaired as you said. Thanks again!