We have several Appian applications with records backed read-only grids which our business users can quickly search, filter, page through to access record instance data. One of the main gripes (over the years) with Appian is that while paging and taking an action on a record, the user has to page back through a series of data sets to arrive where the user initially started the action from. Honestly, it's a bit surprised a paging cache feature hasn't made into a default platform offering in Y2024 but would the Appian community be able to provide examples of how we can implement a "cached paging paradigm" to improve user experience. It's definitely a slight annoyance platform-wise but I'd prefer to hear your opinions and implementation thoughts on how best to improve a one-less-click experience.
Discussion posts and replies are publicly visible
Bumping up to see if anyone could share implementation thoughts on how to best save paging data with records backed grids (a!recordData)?
Hi joet0002 one thought would be Store paging configurations (like startIndex and batchSize) in local variables and use these to set the pagingInfo in a!recordData. This will help retain paging state during the user’s session on the interface.
I believe a!recordData does not leverage the use of an pagingInfo parameter though. How else could we achieve paging?