Question
Murex
LB
Last activity: 25 Oct 2018 2:44 EDT
pxRetrieveSearchData Activity always Triggers the Declare OnChange causing performance issues
Hello,
When we are trying to search on work objects in pega, using the Full Text Search, the pySearchWrapper activity calls the pxRetrieveSearchData activity that always calls most of the declare on change and the triggers causing a performance issue.
Any idea on how we can stop calling the above triggers.
Thanks,
Joseph
***Edited by Moderator Marissa to update platform capability tags***
Pegasystems Inc.
FR
Hello,
Are you sure that performance problem is mainly due to those declare onchange ? Have you tried to trace to check where the time is spent?
Murex
LB
Hello,
the performance is due to those declare onChange, all was showing on the tracer, so how can I stop triggering those onChange when I am using the pxRetrieveSearchData Activity?
Thanks,
Joseph
Pegasystems Inc.
FR
Hello,
Which product version are you using? I don't have this behavior on my side are we talking about Out-Of-The-Box OnChange.
Murex
LB
Hello,
Thanks for your reply.
I have Pega 7.3.1, And it triggers all the OnChange activities making the performance too low and the search taking time to return the results, the Full Text Search OOTB by Pega.
Thanks,
Joseph
Pegasystems Inc.
FR
Right,
Maybe you can try something like this: https://collaborate.pega.com/question/how-disable-declartive-network-resave-activity
Pegasystems Inc.
US
Joseph,
What exactly is changing? I wouldn't expect an onchange to fire without a change to the data and the triggers shouldn't fire unless you are saving that change to the database. Taking a quick look at pxRetrieveSearchData I'm not seeing it doing anything that I would expect to cause either type of declarative to fire. When you trace this, what are the properties to watch or properties that were modified in the declaratives that run? Did you see pxRetrieveSearchData make that change? I suspect there is some other piece to this puzzle, which is why Marc didn't see this problem in his tests, and my guess is the key is in the declarative definitions.
Thanks,
Mike
Murex
LB
Hello Mike,
I would expect it to, that's why I'm asking when I use the Full text search in the portal, all Onchange rules fire and sometimes I get a fail saying that I have to get a lock on the object to perform this action.
There is no change on the properties.
I launch the tracer then I go to the Full text search and type a word==> I see every time the search gets a result or an object ==> it fires all the Onchange rules on it. is it the expected behavior on the full text search?
Thanks,
Joseph