As we are planning to move to V7.x, we would like to know more details about this mechanism against Lucene. Also, we are looking to know the known issues or any precautionary stuff we need to take up before we start using it. In our current V62 environment with compatible CPMHC, the data is huge and Lucene is not the right fit for searching the WO and our folks contacted GCS earlier on this. Currently we disabled this feature in prod but is used in other non-prod environments.To enable this search feature when we go to V7.x, we would like to prepare our-self to show case in front of biz to bring the confidence. If I get as much as info or docs/articles on this ES mechanism, I will make use of it to convince biz. One more thing is that we have purge/arch is in place but still we want to revisit the old data some times.
Starting in Pega 7.1.7, the full-text search engine changed from Lucene search to Elasticsearch.
Compared to Lucene search, where index files are stored and accessed on a single node, Elasticsearch is architected from the ground up for use in distributed environments, and automatically provides a more robust, fault-tolerant search capability. Additionally, Elasticsearch can detect and remove failed nodes in a cluster, and automatically replicates and reorganizes nodes as needed.
Can full “Rule Content Search” be achieved by Pega OOTB “Search” functionalities ?
For example , we want to search the extract Rule Name and its details where a StepPage (e.g "MystepPage") , a hardcoded condition check (e.g if(X==”abc”)), parameter value passed (e.g param.EmpID) etc (all these given as input) is used throughout application.
If Pega OOTB Search functionalities provide these then please refer us how can we configure this in my application?
In designer studio search, you can use the "All Content" option to search if the content of the rule has some specific text or not. You might want to refer to this PDN document - https://pdn.pega.com/release-note/report-definition-query-filters-can-s…. Note that special characters like equals (=) or double quotes (") are not indexed so you cannot search for the presence of those characters in the content.