The following feedback is nothing too urgent, but I believe it would improve the overall UI experience for Citizen Devs and Operators ![]()
- I happen to use table queries very often and change filters constantly. To improve the flow of execution, I suggest a combined button “Save & Test” and for it to be placed in the filter drop down of the query.
-When clicking on a record within a table, it would be useful to have the option to move and re-size the edit record pop up for a horizonal view and still allow left to right and up and down scrolling of the table. One reason for re-sizing to a horizonal layout is that when editing an integer type value, if the user clicks into the box and scrolls up or down while the input box is active, the value will change based on the up or down scroll action. You have to be mindful to click out of the integer box to avoid this. Sometimes I want to edit a record based on another records value, but without re-sizing or the ability to scroll the underlying table, I need to close the edit record box or open another window. This would be a great convenience!
-Within an interactive table, allow the operator to click a column header to expand the column. On a computer this isn’t an issue since you can click, hold and drag the header to extend the length. The problem is on tablets because it’s very difficult to select the correct point on the header to drag, combined with the table scrolling simultaneously.
- While building a table analytic, allow the user to drag operations into a different order. Currently, the only method to change the order of operations / columns is by changing the entire operation.
- Create the option to lock specific table queries and aggregations from being edited based on user logged in. We have many queries and aggregations, and while user roles do play their part, another level of protection would be handy.