Our client is looking to implement Pega Pulse on the case harness, however we’ve observed the search is not working. We’re now trying to understand if there is any setup outside of what is mentioned in the guide - Enabling users to post messages in the activity feed | Pega to search, highlight, and display posts added to the case?
Currently we have observed that Pulse Search is not working in our application, and also not working in a new Personal Edition, and Pega Community cloud where we’ve followed the setup steps.
We’ve observed that while searching a result count is displayed and D_PulseResults pagelist and count is correct for the social feed, but posts do not display on the UI (D_pxPostSearchResults or D_pzFeedParams). Attaching screenshots for reference.
@LuisA379 can you replicate the issue using Pega Platform Enterprise Edition?
→ Which version does your client have installed?
An Issue was identified with the pzSearchPostsWithAttachments activity in 8.7. Some instances were found where the Report filter was not working when there was space in filter value.
This was resolved in version 8.7.4 under ISSUE-727704.
Also be aware that the current design of search in PegaSocial Pulse is such that we can only search for posts made by operators for same application. So User A cannot search for / find posts made by User B since B is from a different application. This is because while adding Pulse messages, pxApplication is populated from pxThread.pxCurrentApplicationName field. Enhancement request FDBK-91271 exists for that.
Can you check the log files and run a tracer to see if there are any errors when entering pulse notes?
Your tracer should be able to see the results from pxRetrieveSearchData Activity that after pxRetrieveSearchData it is calling pxRetrieveReportData. Go through the D_pxPosts Data page from where pxRetrieveReportData is called, there is a filter with application name and the posts posted by certain user the application name.
If Pulse pzFeed section is throwing errors you can try Bulk validate and save the rules.
Re-Save the rules corresponding in the error logs. (You may use Re-validate & Save option) and also rebuild the Vtable cache (using the REST API) for the corresponding rules for the below java classes.
