Hi all,
If you have a small instance or a small Knowledge Base or hardly any changes on your Knowledge Base, you could maintain the Connected Content on Employee Center Topic manually of course. Just adding Knowledge articles as Connected Content. And most likely, directly in production. Since both Knowledge articles and Connected Content are data.
Though what if you have a large Knowledge Base or continuously a lot of change in your Knowledge Base. How are you maintaining this? Just wondering how others are doing this 🙂 I mean, if you have hundreds of Knowledge Bases, ten thousands of Knowledge Articles, maintaining such manually might be painful.
You could definitely think of some Business Rule or Flow logic to automatically maintain Connected Content, though out-of-the-box there's also no reference or something on a Knowledge Base (or Category) to a Topic?
And what if you have exceptions... like not having all Knowledge Articles under a certain Knowledge Base on your Employee Center Topic?
And if something custom like this in place, would you actually map a Knowledge Base to a Topic, or rather map Knowledge Categories to Topics? When you would have a new Knowledge Base (or Category), you might need a new Topic. You could generate such scripted or something, though a Topic is NOT data, so then you would not do that in production? (and you might want to govern your Topic structure, the naming, an image, a description)
Just wondering how others are approaching this 🙂
Kind regards,
Mark
