Improvements to search functionality?
What Michael Degatano said, 3 years ago -- Rethinking Search for 7.1
Which of these have been done? Which are addressed by v7.1.8 Elastic Search?
A couple of things I'm still running into now, that are still problems as of v7.1.5 (yes, ancient, I know):
- When the search runs into a java.net.SocketTimeoutException, there's no message to the user about the problem (see Standard for User Error Messages?)
- The choice of context vs. name search is fairly important predictor of how long the search will take. But there's no UI to toggle those until after you search.
- Can that be included in the search bar?
- One trick, I know, is to preface searches by "old:" to search the names directly.
Pegasystems Inc.
IN
Hi Jon, Good Morning!
We could limit our rule search based on class name as below ...
<RuleName> AND pyClassName:*<ClassString>*
Example: pyDefault AND pyClassName:*PegaSample-Repair*
Thank you!
psahukaru
Pegasystems
IN
When the search runs into a java.net.SocketTimeoutException, there's no message to the user about the problem
There is no such exception with ElasticSearch in 7.1.7 as we don't use SOAP / HTTP connect / service anymore.
Which of these have been done? Which are addressed by v7.1.8 Elastic Search?
Elastic Search was introduced in Pega 7.1.7 to provide automatic fail over for full text search which was not feasible with Lucene. What Mike has suggested are usability enhancements to search as a feature in the core product. All those features are in the pipeline. I will pass on your feedback to product management so that they are aware of this.
Finally, the Lucene syntax does work (like described in the document by Mike Degatano) even with Elastic Search.
BNY Mellon
US
follow-up question here as well: Customizing the search index