Hi,

In our application we are feeding two tables in the same screen using a single page list, to do that we use the Row visibility, for example:

Optimized code: [x]

Row visibility: Condition (expression) .TypeCode = "Type A"

[x] Run visibility condition on client

Our table –which uses optimize code checked– also have sections in the columns which are refreshed depending on changes in other columns, for example changing the dropdown might set a rate in the contiguous column.

Now consider the following initial data and configuration:

Page list with 22 items: 20 of "Type A" and 2 of "Type B"

Pagination page size set to 10.

Based on the described above, these are the issues we have found:

• If Run visibility condition on client is unchecked and you change a value in the column (which makes a refresh of a section embedded in a different column) and then go to the next page, the pagination breaks/disappears. (this issue does not occur if you enable Run visibility condition on client)
• If Run visibility condition on client is checked, then the pagination is inconsistent, for example: you might get the first page with 7 items (it should be 10), the second page with 10, and a third page with 3 items... other times you can get the first and second page with 10, but a third page with 0 items.

For the second bullet above, is like Pega is aware the page list size is longer than 20 items, which it is, but it should not count the extra two items because there are of a different TypeCode = "Type B".

Thanks for any ideas or insights on this!

Regards,

-Jose Navas