Question
Saltech
GB
Last activity: 8 Jul 2019 4:17 EDT
Pega 7.2.0 Steps to Configure Elastic Search
I am trying to understand how to configure the elastic search for an end user portal. The aim is to allow a full text search and then to display this in a grid on the UI much in the way the rules search works in the developer studio.
The steps I have followed so far are...
1. Enabled the dynamic system setting indexing/useDataInstances
2. Created an instance of Data-CustomProperties-Search specifying some embedded properties. These are to be shown in the search results.
3. Created a report definition in the framework class of the work items I am searching for. This is configured to report on descendant classes. The columns defined in the report definition include some of the properties in the instance of Data-CustomProperties-Search that I created.
4. Create an activity to call pxRetrieveSearchData passing into that the search string and the report definition class and name.
5. I have reindexed the work index via the search landing page.
6. I have checked that FTSIncrementalIndexer is running.
The search is not working so what am I missing? I can see the activtiy running and if a basic search string is entered such as "a" then it brings back some results, however if some data is entered that I know exists on a case then nothing is returned.
The assumptions I had in terms of operation of the elastic search were:
1. All the data in the work item is stored in the index.
I am trying to understand how to configure the elastic search for an end user portal. The aim is to allow a full text search and then to display this in a grid on the UI much in the way the rules search works in the developer studio.
The steps I have followed so far are...
1. Enabled the dynamic system setting indexing/useDataInstances
2. Created an instance of Data-CustomProperties-Search specifying some embedded properties. These are to be shown in the search results.
3. Created a report definition in the framework class of the work items I am searching for. This is configured to report on descendant classes. The columns defined in the report definition include some of the properties in the instance of Data-CustomProperties-Search that I created.
4. Create an activity to call pxRetrieveSearchData passing into that the search string and the report definition class and name.
5. I have reindexed the work index via the search landing page.
6. I have checked that FTSIncrementalIndexer is running.
The search is not working so what am I missing? I can see the activtiy running and if a basic search string is entered such as "a" then it brings back some results, however if some data is entered that I know exists on a case then nothing is returned.
The assumptions I had in terms of operation of the elastic search were:
1. All the data in the work item is stored in the index.
2. The report definition is to specifiy how the results should be returned.
3. The intances of Data-CustomProperties-Search are to allow those properties to be referenced in the report definition and included in the results of the search of the index.
4. I have rebuilt the Data- and Work- indexes however I assume that for embedded page properties in a work class then the Work- index is sufficient for this.
5. Instances of Data-CustomProperties-Search will be inherited. So I can define these in the Framework layer class and it is not needed to create the same in the implementaton classes.
Pegasystems Inc.
US
Those steps seem okay to me... Though I'm not entirely sure about the inheritance part. Could you try creating a custom search property instance in the implementation class, reindexing that class, then see if it works?
Saltech
GB
Thanks for the help.
Would you have any idea on the questions I posted below?
Questions
- We want to be able to search the entire workpool without having to create a separate report definition for each child. Is this supported as it seems like the inheritance is not working when the report definitions are used in the elastic search.
- We have observed that for a embedded property on a page 1 level deep i.e. Work.EmbeddedPage.Prop then this is returned and populated in the search results from the elastic search. If we configure a property in the same way but the data structure is as follows Work.EmbeddedPage.EmbeddedPage2.Prop then although we can search on this it is not returned in the report definition results so we can't display the data in our grid. Is this supported?
Saltech
GB
Some progress has been made.
Steps taken
- We had a queue item for the FTSIncrementalIndexer agent in the 'Now-Processing' queue that appeared to be stuck, it had been there for over a month. Once we removed this and reindexed then there was a definite change as the reindexing took a lot longer. No errors were in the logs previously or shown via the designer studio landing page however this clearly wasn't working correctly.
- The report definition
- Initially created in the framework class at the work pool level and still no results.
- Moved the report definition to the implementation layer at the work pool level - still nothing.
- Move the report definition to the actual class of a work item. Now its started to return results.
What we are trying to achieve
We would like the users to be able do a full text search on any case type within the work pool. We want to avoid having to have a drop down to specify the type of item to be searched for.
Questions
Some progress has been made.
Steps taken
- We had a queue item for the FTSIncrementalIndexer agent in the 'Now-Processing' queue that appeared to be stuck, it had been there for over a month. Once we removed this and reindexed then there was a definite change as the reindexing took a lot longer. No errors were in the logs previously or shown via the designer studio landing page however this clearly wasn't working correctly.
- The report definition
- Initially created in the framework class at the work pool level and still no results.
- Moved the report definition to the implementation layer at the work pool level - still nothing.
- Move the report definition to the actual class of a work item. Now its started to return results.
What we are trying to achieve
We would like the users to be able do a full text search on any case type within the work pool. We want to avoid having to have a drop down to specify the type of item to be searched for.
Questions
- We want to be able to search the entire workpool without having to create a separate report definition for each child. Is this supported as it seems like the inheritance is not working when the report definitions are used in the elastic search.
- We have observed that for a embedded property on a page 1 level deep i.e. Work.EmbeddedPage.Prop then this is returned and populated in the search results from the elastic search. If we configure a property in the same way but the data structure is as follows Work.EmbeddedPage.EmbeddedPage2.Prop then although we can search on this it is not returned in the report definition results so we can't display the data in our grid. Is this supported?
Our case structure is like the following:
CaseA (Abstract)
CaseA-CaseB (Concrete, inherits from A)
CaseA-CaseC (Concrete, inherits from A)
So we want to put the generic report at the case A level.
Pegasystems
IN
Questions
Questions
- We want to be able to search the entire workpool without having to create a separate report definition for each child. Is this supported as it seems like the inheritance is not working when the report definitions are used in the elastic search. Yasaswani : We do support searching against workpool . We check whether the class on which RD was defined is either a classgroup or not and construct the query.
- We have observed that for a embedded property on a page 1 level deep i.e. Work.EmbeddedPage.Prop then this is returned and populated in the search results from the elastic search. If we configure a property in the same way but the data structure is as follows Work.EmbeddedPage.EmbeddedPage2.Prop then although we can search on this it is not returned in the report definition results so we can't display the data in our grid. Is this supported? Yasaswani : This as well is a supported feature . Can you raise a support request for the same so that we can further analyze this?
Pegasystems Inc.
US
When you open the SR as suggested by @KODUY above, please reference this PSC post and then let us know the SR Id so that we can track for you.
Thank you!
Saltech
GB
Update:
So far we have observed the following behavior.
1. A report definition with Joins in does not appear to work when used with the elastic search.
2. The search properties required to be displayed in the results (and hence in the report definition) do not have to be exposed in the database to work.
3. Due to the above (#2) it is not necessary for the report definition to be able to run on its own to be able to be used in the elastic search.
4. The report definition needs to be placed on the class that is being reported on. The descendant classes option doesn't appear to work even if placed in the same workpool in the same layer (implementation).
5. The pattern of a certain level of nested objects does seem to be a factor. When the same properties were copied up a level and configured in exactly the same way then it works.
Cognizant Technology Solutions
US
I am adding the issue i had. configured a data class but index didn't worked. the below solved my issues.
on the “Advanced” tab of the concrete Data class that needs to be indexed, add a Harness rule . May be a dummy Harness also works.
Scope International
SG
Can any one advice , can we use Assignment tables in elastic search. To improve the performance while loading the Work list and work basket results as we have huge data in tables.
Virgin Media
GB
It would be very nice to have this, but I do not believe the functionality is there for those classes unfortunately as we'd like to make use of that also. But any joins within report definitions even with the latest version 8.2.2 still go back to the database.