We are carrying out a procedure for a client to improve the performance of a screen where they need to retrieve workbasket information for their operation.

Using Constellation, a landing page (TemplateList page) was structured to obtain the data from the work table.

This data was designed to be retrieved through a data page that reads a report definition to obtain the information to be displayed on the screen.

When using the feature in its standard form, we have no limitations when applying filters, sorting, or grouping on the screen. However, due to performance limitations—since the data load times were very high—we decided to implement Infinite Scrolling to enable pagination when loading the information and improve the response time.

We found that the filtering functionality stops working, as well as sorting. Since some fields do not come directly from the work table but rather from the use of indexes in the report and joins with the workbasket table, we believe there may be a limitation in using Infinite Scrolling. Using the debug tool, we verified that for fields not directly from the work table, they are identified as page objects and not as fields, as shown in the evidence below:

Any action or modification needed so that we can use infinite scrolling properly? Will we need to create a single table structure to address this point?