On a current project, we're defining how portal content will be set up and displayed. There is concern with how much effort would go into managing all of this. What a coincidence! There is a new tool available in the July 2025 release that helps manage outdated portal content. But how does it work? I normally do backtracking through new features like this to understand how they are put together to help with demos, setup and implementation.
So Connected Content Management starts with a left nav item that links from the Outdated Connected Content link to a UI Page for outdated_connected_content. It's pretty straightforward and the URL of that page contains an encoded query that defines what is shown on the page is built from the TaxonomyUtilAjax script include.
That script include is where the details of the query are put together and it calls out to the taxonomy_content_configuration table to pull in the conditions that make up outdated content. The records in this table show up in the documentation as "admins to define what qualifies as outdated, such as retired knowledge articles or inactive catalog items, using configurable filters."
The conditions are stored in here in the Conditions field and are then concatenated to the URL to define the encoded query which makes up the definition of Outdated Content.
Hopefully this helps someone digging into this feature!
