- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2019 04:32 AM
I am hoping someone can help with the below issues we found when testing knowledge versioning.
We have tested Knowledge article versioning in our test environment and at this time we can't use it because:
- As soon as an article is checked out an approval email is sent out, even before the new version is published
- Knowledge bases that have no approval in their flow will never go to the next number version, 1.0 will go to 1.1 and not 2.0
- Unable to change any of the metadata on the screen without a new version,, when we change our valid to date we do not want a new version number
Solved! Go to Solution.
- Labels:
-
Knowledge Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2019 04:53 AM
Hi...I can help with the third bullet. There is a knowledge property for Minor Edits that needs to be enabled. Browse to Knowledge-->Administration-->Properties and locate the "Enable minor edits to the published article without creating a new version." (glide.knowman.versioning.enable_minor_edits) Click the check box to enable it and then click save.
As for the first bullet, sounds like there may be something wrong with the workflow or it was changed from the out of the box workflow.
For the 2nd bullet, all of our KB's are approval Publish workflows. If you have a personal developers instance, you may want to compare the behavior in your personal Dev instance (assuming it is out of the box) compared to your company's instance.
Hope this helps!
Jeremy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2019 04:53 AM
Hi...I can help with the third bullet. There is a knowledge property for Minor Edits that needs to be enabled. Browse to Knowledge-->Administration-->Properties and locate the "Enable minor edits to the published article without creating a new version." (glide.knowman.versioning.enable_minor_edits) Click the check box to enable it and then click save.
As for the first bullet, sounds like there may be something wrong with the workflow or it was changed from the out of the box workflow.
For the 2nd bullet, all of our KB's are approval Publish workflows. If you have a personal developers instance, you may want to compare the behavior in your personal Dev instance (assuming it is out of the box) compared to your company's instance.
Hope this helps!
Jeremy