Details
-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
2
-
L
-
3 - Expected
Description
What is the desired functionality that you are missing?
As a User I would like to create Process Reports that are visualized as tables and look at more than 10.000 data points. This can be achieved by implementing backend pagination for these reports (which might also come with other improvements (e.g. performance / evaluation time of reports).
Which problem are you going to solve with this functionality?
Today when evaluating reports (with visualization table) that have more than 10.000 results there is an error shown to the end user.
In table visualizations however, evaluating such report can make sense for the user. We already support this for Raw Data Reports. It is unclear to our end users why this is not possible for other reports visualized as tables.
Acceptance Criteria
- MH: A high max limit is set for the number of rows displayed in a table report
- MH: The table loads even if the max limit is exceeded
- MH: The number of rows is always available
- NTH: Users can request another page or all pages
Hint:
While we are at this we should also evaluate how paging can actually be supported on other visualizations.
The "high max limit" can be 10k - that's appropriate. The point of the AC is to quickly revisit (2hr spike) our limit
