I recently came across a task that would take a very long time to execute when performed on 1000+ rows at once, not because of the task itself, but because the context was being performed for each row and taking some time. Luckily I could find a way to improve the context, so the wait time is down from minutes to a couple of seconds, but still I think in those couple of seconds to users it might appear that the application is unresponsive and it would be good to show a process is running when a task is being staged.
Solved
Show a loading bar while stage requests are being performed
+4- Sidekick
Best answer by Arie V
+12
Hi Robin,
I have question about this. How did you select a 1000+ rows? Are those basically a select all on specific filterered set?
Sebastiaan
+4- Sidekick
Hi,
Yes, that is correct. The user filters the data and then selects all rows. The task is has a multirow XML parameter, calculates new rows based on the selected rows and inserts them into another table.
I think in the Windows app it worked a bit different and the context was not executed per row?
We think that Universal and Indicium together could handle this more like the Windows app when we know all the rows within a filter are selected. That is why I wanted to verify how the user selected those rows.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.