Will it be possible in the future to apply Infinite Scrolling to certain Card Lists, Form Lists and Grids in our applications? We would like to see it as an extra option in subjects.
For some screens it is desirable to have this, especially for small mobile devices, this can gain some extra available height, and avoid scenarios like below:
Is this technically feasible or are there good reasons not to want this?
Or is this something that can now be achieved in the Univeral GUI, using custom CSS?
Hi Harm,
I’m a big fan of infinite scrolling. However, this is not something that can be done using CSS. I would assume the ‘Max nr. of records’ setting would limit the scrolling?
There are some challenges.
One of the things that the GUI does pretty well is keeping track of the active row. When you add or update a record, change the sorting or use a process flow to jump to a certain row, it first determines the page that this record is on and quickly jumps to this page. I wonder how this would work in an infinite-scrolling scenario. If the active row is found very far down, it may be detrimental to load the full dataset up until this row.
Another challenge is so-called ‘sharding’ of the data set. When you load the first segment of data and scroll down a minute later, records of the first segment may have moved to the second segment. This may be due to new data or changed values. Basically, anything that can affect the sorting. This results in duplicate records in the full data set loaded by the GUI.
Vice-versa can also happen, when records in the second segment have moved to the first segment, they will not show up in the GUI when you scroll down a minute later, when the second segment is appended to the full data set in the GUI.
What are your ideas on this?
Hello Anne,
Good to hear that you also see the benefits of infinite scrolling.
We can now set page size to, for example, 1000 and because the performance is so good, that it appears to work fine for end users, but then of course far too much data is sent over the line. It could give problems on low-band widths.
I hope that there may be conditions where infinite scrolling is preferred over pagination. In that case the GUI could perhaps also apply infinite scrolling automatically.
Perhaps the condition could be that infinite scrolling can be enabled if sorting is fixed and filtering is disabled for the table. Maybe also make it only work for card lists, as these are always read-only?
There will of course be quite a few challenges, but I think it should be technically feasible. In any case, it would be a very valuable addition to the platform and we expect great appreciation from customers and end users.
For your information, we are trying to build a kind of integrated chat function around business processes, as you see in many social platforms. This eliminates a lot of email traffic and therefore contributes to sustainability.
Do I need to make an Idea for this, or is it already on the road map?
I’ve converted the topic to an idea. Don’t forget to vote!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.