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
This feature has made it into the platform in Y2024.
https://docs.appian.com/suite/help/24.3/url-parameters.html
Just wanted to follow up on this as I have seen similar posts referencing the same question on paging behavior. How would we approach a URL parameters paradigm with a records data-backed grid? The a!recordData function does not currently support a pagingInfo parameter so I'm curious on how we could achieve caching while maintaining the benefits of a records backed grid (userFilters, showSearchBox, showExportButton, etc.). Assuming here that we would and pass in a startIndex variable through an interface rule input on a portal/or site.