Tokyo feature - Retire knowledge blocks that are still used by articles

[Sam Goode]

In Tokyo, there is now a property (glide.knowman.allow_retire_block) to allow knowledge blocks to be retired, even if they are used by articles. 

This avoids the common issue of not being able to retire a knowledge block that was used in a previous version of an article (which could no longer be easily edited).

Retire a knowledge block (servicenow.com)

When retiring a knowledge block, you will now see this confirmation message:

[DavidBReynolds]

Is there a way of tracking which articles link to each block?

Before I retire an article, I run a report with the article number listed as being in the body. When I find matches, I remove or replace the links.

Can I assume a method like this is required to identify articles containing retired blocks?

[mbernste]

I created a report that lists the knowledge blocks and what articles use them.  I used the m2m_kb_knowledge table.

[BukkapatnamAsh]

@DavidBReynolds , yes, you can track the list of articles.

if you open knowledge block in Next Experience, you will have Articles tab at bottom of the screen. Under that you will have list of articles used by the Knowledge block.

You can create report using m2m_kb_knowledge_to_block table.