Unresponsive UI after applying table column filter
Hi,
Recently, I'm troubleshooting an issue with our Pega application, the issue is when we apply a filter in some of the columns, then the UI becomes completely unresponsive: clicking another button in some other place, trying to clear the filter, trying to run the tracer, nothing works. The only way to restore the UI is to do a refresh from the browser.
I've tried checking the logs and running the tracer at the time of applying the filter, but I don't see anything unusual or marked as an error.
As I mentioned the issue only happens for some of the columns, not all of them. We also manage a lot of data in this table and is sourced by a Data page with a report definition which also refers to a declare index table.
Thanks for any thoughts on this,
P.S. Adding browser's console error
-J Navas
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
IN
Hi @josenavas,
Can you please provide more information on the configuration of the table?
- Is there any pattern between columns where the filter is working and columns where the filter is not working? - Are the columns coming from RD or calculated ones?
- Do you see any error pop-up window screen?
- Type of the Data Page and any relation between keys to the DP and columns on the table?
I have tried a scenario and cannot replicate the issue. I anticipate some patterns for the columns for which UI becomes unresponsive.
Updated: 10 Oct 2022 16:02 EDT
SoftServe
US
@siris2 thanks,
Let me try to answer your questions:
Can you please provide more information on the configuration of the table?
Table has Personalize table enabled (allow) so you can show/hide columns as desired by the end user. Main data source is a Data page.
Is there any pattern between columns where the filter is working and columns where the filter is not working? - Are the columns coming from RD or calculated ones?
I thought issue might be related to embedded pages used to display some of the columns, like ".Customer.FullName" (these are processed in the response DT) however there are some columns with different embedded pages that work good and they let you apply the filter and continue using the UI; Most of the columns are pre-processed for display in the response data transform of the Data page source.
Do you see any error pop-up window screen?
No errors appear on the UI, tracer or the Pega logs, but I can see some errors in the browser's console. (Attached in my initial post)
Type of the Data Page and any relation between keys to the DP and columns on the table?
Data page's structure is List, Mode is Editable, and Scope is thread. We don't use keys in the DP, just two parameters.
Recently, I found I can unfreeze the UI by clicking a different column –a sort on that column is performed– so the UI can become responsive again.
@siris2 thanks,
Let me try to answer your questions:
Can you please provide more information on the configuration of the table?
Table has Personalize table enabled (allow) so you can show/hide columns as desired by the end user. Main data source is a Data page.
Is there any pattern between columns where the filter is working and columns where the filter is not working? - Are the columns coming from RD or calculated ones?
I thought issue might be related to embedded pages used to display some of the columns, like ".Customer.FullName" (these are processed in the response DT) however there are some columns with different embedded pages that work good and they let you apply the filter and continue using the UI; Most of the columns are pre-processed for display in the response data transform of the Data page source.
Do you see any error pop-up window screen?
No errors appear on the UI, tracer or the Pega logs, but I can see some errors in the browser's console. (Attached in my initial post)
Type of the Data Page and any relation between keys to the DP and columns on the table?
Data page's structure is List, Mode is Editable, and Scope is thread. We don't use keys in the DP, just two parameters.
Recently, I found I can unfreeze the UI by clicking a different column –a sort on that column is performed– so the UI can become responsive again.