Hi,
In PKM Portal, our customer want to search without filter on status but it seems not possible
Existing behavior allow to search article but the filter status is mandatory.
There is two aggregate status “Awaiting Publication” and “Active Statuses” that allow to search on multiple status; but there is not aggregate value like “All Statuses”.
In attachment a screenshot of the standard screen
I check the rule behind the search and it’s not possible to customize it (details: it’s possible to customize the UI by adding a value like “All Status” in property KMpyStatusWork but it’s not possible to customize the activity “KMSearchContent” - data source of data page D_ExportContentList used to display the article search result. Indeed, this activity is Final and I can’t consider the new value of property inside).
So I have two questions:
- Do you know if an OOTB behavior allow to search PKM article without filter on status ?
- If no, is it possible to make the activity “KMSearchContent” as Available to allow customization on search behavior ?
- Otherwise, is it possible to implement a change to add the value “All Statuses” in the list ?
@JOHAN.GRALL 
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Your request is currently not possible with the standard configuration.
After researching your questions, here’s what I’ve found:
Regarding your first question about an OOTB behavior to search without status filtering - from my investigation, it appears that the standard PKM Portal search is indeed designed with mandatory status filtering as you’ve discovered. The system currently only supports the two aggregate statuses you mentioned: “Awaiting Publication” and “Active Statuses.”
For your second and third questions about customizing the KMSearchContent activity - this is more challenging since the activity is marked as Final. In Pega, Final activities are deliberately locked to prevent modifications that could impact core functionality. While you’ve already tried the UI approach by adding an “All Status” value to the KMpyStatusWork property, you’re correct that this doesn’t help if the underlying activity can’t process this value.
Based on this situation, here are some potential approaches:
- Extension Points: Rather than modifying the Final activity directly, you might want to investigate if there are any extension points or pre/post-processing activities that could be customized to achieve your goal.
- Custom Search Solution: Consider implementing a parallel custom search functionality that could bypass the status filter requirement if the standard search can’t be modified.
- Service Request: Since this involves modification to core functionality, you might want to submit a Service Request through Pega Support to explore if there’s an official way to implement this change or if it could be considered for a future release.
- Technical Workaround: If you have access to the database level, you might be able to create a custom report or data page that retrieves articles across all statuses, though this would be separate from the standard search interface.
I apologize that I couldn’t provide a direct solution to modify the KMSearchContent activity. This appears to be a limitation in the current product design that would require deeper technical intervention or product enhancement.
References:
