Not sure if it was brought up already on other occasions but currently, the interactive table widget does not remember its state when it gets re-rendered (scroll position vertical/horizontal), selected page, etc…
When it is used for record selection purposes this can quickly become a daunting limitation for the operators if they constantly have to manually find their way back to the “old state” prior to a re-render.
Concrete example: An operator needs to cycle through a couple of records to check state and this state check requires a more elaborate trigger change to run which is “outsourced” onto a dedicated step for visual feedback and modularity. In this case the operator selects a record, is then sent to the processing step, the processing step cycles through the trigger chain and transitions back to the original screen. When there, the original state of the widget is lost, while the placeholder record may still be populated… but it is now berried in “some page”…
Instead of burying the triggers on a separate step, couldn’t you place it on a custom widget instead and activate when operator selects a row? I mean to avoid the step change?
I am suggesting this even though we avoid using custom widgets to stick to the standard set of functionalities and avoid custom code on the platform.
It was just an example. But there can be other cases where it would be very beneficial to have the state in memory rather than a re-render. At least as long as there has not been a dedicated app completion. And yes, I would not like to have to introduce a custom widget for something like this.
With particularly large tables that allow for record selection, it would be helpful if a user returning to the step that contains the table is brought to the page in the table that their selected record exists on.
To clarify, if I select a row in a table beyond the first page, proceed to the next step, and then have a reason to return, the step loads showing the first page of the table. Loading the step and showing the page on the table that the selected record is on would be really useful.
Thanks for bringing this up—Acknowledge your really valid feedback here on how re-rendering and manually finding your way back to a previous state can be inconvenient. Improving this behavior is on our radar, and we’re investigating on ways to how best to address it.
In the meantime, it would be super helpful if other community members could like or comment on this post to help us prioritise this work.
Thanks for the input!
Cana