Hi,
In some part of the UI, when choosing the number of records to display per page, it’s possible to select “all of them”. Like, for example, in the service configuration page :
When this number is high, it makes the UI unusable (it timeouts).
It shouldn’t be possible to select a value that is impossible to display. In another hand, 100 is too low.
Maybe the available choices could be something like : 10,20,30,40,50,100,500,1000,2000,3000,4000,5000 ?
+18
+15Hi
For what purpose do you display high numbers of resources? For massive changes or just for viewing the items?
It’s easier for massive changes, also to view the items. Although a very big number of items could make the UI unresponsive, it’s possible to display a lot more than hundred items. A few thousands is OK.
For massive changes this is not only easier, because doing a massive change with a selection on multiple pages doesn’t work.
+18What about instead having a massive change that applies to the current query/filters without displaying all items (typically when applying a change you’d be asked if the change only applies to the currently displayed page or to all pages?
A functional massive change on a selection on multiple pages would be great. IMO, we don’t need to let the user chose between two kinds of massive changes. If he selected items on multiple pages he’d probably always wants those items to be included in his massive change. Two different massive change modes seems an unnecessary complication to me.
But, what would be nice, is a confirmation dialog that shows the number of objets the massive change is going to modify. This way, if the user forgot he had selected some objects in another page, and doesn’t want them to be included in the massive change anymore, he can avoid a potentially wrong action. In addition, a way to deselect all objects (through all pages), would be useful.
+18No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
