In a prior Pega server/application of ours, the Scheduled item count in the SMA's System Queue Management was managed to reduce the count by turning on the SystemWorkIndexer agent, to allow pulling of the items off the queue even though the work was not indexed. This approach is not reducing the count in a new Pega server/application. We are in Pega 7.1.6. The count increases daily, about 10,000 per week. What would be the current approach to bring that count down and get the items processed?
Message was edited by: Kip Jackson - Removed SR reference from the discussion - Added related work with the SR# - Modified the Discussion Title
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Go to the search landing page and disable "Data” indexing. Not data instances will be returned in designer studio searches and instances of Data-Social-Tag will not be shown in the work search gadget.
Check the search landing page to see if the right node is set for indexing and search. If not, fix that and ensure that the SystemWorkIndexer agent is running. You can do both of them from the search landing page itself.
Posted: 7 years ago
Posted: 16 Jul 2015 7:45 EDT
Jeff Gray (JEFFGRAY)
Thanks for the reply. I have an update. We discovered the increase in item count was because an increase in case inventory pushed up the count in PR_SYS_QUEUE_SLA. As inventory is worked, this will decrease our Scheduled Item Count.