Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1910 Ideas

JoostRookie

Add grid views (in addition to prefilters)Open

Context  To create different grid layouts (i.e. active columns, sort order, fixed columns, etc) for users, we now have to rely on developers (i.e. design-time) to create Variants. Variants are a good way to also control many other things in a screen, but oftentimes users only want a different grid layout (mostly when they change a prefilter) while the rest of the screen must remain the same.  An example of this is when a user switches between working with open sales-orderlines or invoiced sales-orderlines:  When working with open sales-orderlines, the invoice-ID-column is not relevant but showing the available stock columns is.   When working with invoiced sales-orderliness, the invoice-ID-column is relevant but the available stock column is not.   It is currently also not possible to not have only a selection of all possible columns activated when a user opens a screen for the first time (now default behavior is all columns are active and this cannot be controlled).   Feature request We ask for the ability for end users and application managers (in IAM) to save and share Views at runtime. Views will live directly next to prefilters and the combination of both is very powerful.  A view will be able to store and retrieve:   Visible columns / column sequence  Column width  # Left pinned (frozen) columns (make this user-controlled)  Column sorting (single/multi-sort, sort direction)  Grouping settings (if user controlled and made possible in future Thinkwise release)  Paging size (if user controlled and made possible in future Thinkwise release)   Additional features:  Have the option to load a view, change settings in the grid, and save the new settings over the existing view or as a new view.   At least 1 view must be the default view.   When managing views (in a pop-up-screen), have the option to set one or more default prefilter(s) for the view.   When managing prefilters (in a pop-up-screen), have the option to set a default view for the prefilter.   Using IAM, an application manager should be able to copy a view that a (key) user created and promote is to a ‘standard view’ for a screen-variant/user-group combination. This achieves that certain ‘standard’ views can be distributed to user teams centrally.  

Keep state of document when switchen between "Open documents" in the menuNew

When for example working in the Software Factory, it is not strange to swap between the multiple opened documents. Unfortunately that also means that certain states get returned to their default.Ex:1) You have the Subject entity open and are looking at the columns tab. You have moved your horizontal scrollbar to the right to see the “Context input” column. After having checked something in another document and return to the Subject entity, the scroll bar is again at the start and the “Context input” is again out of sight. Similar behaviour for vertical scrolled grids or forms.2) Another example is the process flow design. You are zooming out to make some space where you intend to put new actions and have some room to move stuff around if needed. After returning it is back to a zoomed in state to just fit all placed actions inside.3) Last example is one of the more annoying ones, which might not entirely fit in this idea as it probably has another cause. You are working on a functionality and have your template open in your IDE and the Thinkwise Workspace Listener is keeping you saved changes in sync. You deploy the current saves state and notice an error. You get back to your IDE to correct this, as the file is still opened, and now the file does not save as it is disconnected.Please keep the state of the document to what it is when leaving it to go to another document, so you continue with what you were doing there.