Pega Knowledge Constellation migration best practices

The following is a list of best practices you must consider when you migrate your UI-Kit KM application to Constellation:

1. You must run the taxonomy path utility kxUpgradeTaxonomyForAnyrole as first step in your migration process, so that the Taxonomy Path property populates before users start working in the Constellation application. This activity updates the taxonomy data and ensures that the List and Taxonomy Paths are correctly populated and available on the Taxonomy landing page of the Constellation application. Use the search function to find the utility, then click Rule actions > Run.
   
2. Ideally, move all in-progress articles to the Resolved-Published status before you switch users to the Constellation application.
3. Do not edit the same article in both the UI Kit application and the Constellation application. Once you edit an article or move it through an approval process in the Constellation application, continue to manage that article in the Constellation application.
4. Complete in-progress drafts in the same application where you started them. Do not move a draft between the UI Kit application and the Constellation application before publishing it.
5. Continue to manage language configuration in the UI Kit application, since the Constellation application currently does not allow users to modify default languages.
6. Enable ingestion to Pega GenAI Knowledge Buddy™ for published content in Infinity Studio by making sure the configuration Enable Knowledge Buddy published content indexing is set to true. Note that in-flight ingestion is not supported, so content must be published before it ingests.
   
7. Build the implementation application manually rather than by using Pega GenAI Blueprint™. Pega Knowledge has specific requirements that Pega GenAI Blueprint™ does not yet fully support.
8. A user with the appropriate access roles can freely switch between the UI Kit and Constellation applications by clicking the Switch application button in the upper left corner of the KM portal.
   

For features that are not yet available in the Constellation application, such as help sites, continue to use the UI Kit application for those specific functions, while you use the Constellation application for content and taxonomy management tasks. As an example, if your organization relies on help sites to publish curated collections of articles for customers, continue to manage help site configuration in the UI Kit application, and use the Constellation application for the day-to-day authoring, approval, and publishing of the underlying articles.