Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Knowledge Management v3 migration

Log in to subscribe to topics and get notified when content changes.

Knowledge Management v3 migration

Knowledge management is significantly changed with knowledge v3, which is enabled by default for all instances starting with the Fuji release.

Knowledge v3 has several key differences from the version of knowledge management available with the Eureka release, knowledge v2.

When upgrading from Eureka or earlier, you must migrate legacy knowledge content and any customizations you have made in the Knowledge Base application in order to use the full range of new functionality.

This video demonstrates how to migrate from Knowledge Management v2 to v3.

Table 1. Key differences
Legacy Knowledge Knowledge v3
One knowledge base. Multiple knowledge bases.
A single lifecycle workflow shared by all articles. Separate, customizable workflows available for each knowledge base.
Two-level organizational structure with Topic and Category. A single organizational taxonomy shared by all articles. Category structure with any number of levels. Each knowledge base has a unique category taxonomy.
Permissions defined per article using roles and ACLs. Permissions defined per knowledge base using user criteria.

Knowledge Management v3 migration process

When you upgrade from Eureka or earlier, consider a multi-step migration process. This process ensures you can access existing knowledge content and allows you to fully migrate at your own pace.

Review automatic changes before upgrading. These changes are applied immediately when upgrading and may impact existing functionality.
  1. Migrate knowledge functionality to use your customized functionality with the knowledge v3 enhancements.
  2. Migrate knowledge content to use the knowledge v3 enhancements with your existing knowledge articles.