Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1967 Ideas

Barcode scanning without needing focus to a fieldOpen

ContextBarcode scanner devices basically work as a normal keyboard attached to a phone, meaning it needs focus at some place on the screen where to put the scanned barcode. With barcode scanners with a touchscreen, it is very easy to unintentional lose the focus on the barcode field (even when there is only one editable task field and a default that sets @cursor_to_col_id), which will insert the barcode in the wrong field or not at all. For production/warehouse workers, this is simply not workable since scanning a barcode should just work without having to even look at the screen.IdeaWith this idea I would like a solution to make a fail-proof barcode scanner with the universal GUI which isn't limited to requiring focus on a specific field. In fact it should be optional to even show the barcode field to the user, since most times a barcode doesn't say much to the user.Possible solutionA possible solution could be a setting at a tab-task. When a screen with that tab-task is opened in the Universal GUI, it will catch keyboard input and execute the task with the scanned input in the first parameter with a barcode domain. When there are more editable fields in the task, the task should not execute directly but open (with the barcode field filled in) so that the user can give input for the other parameters. Side notesImportant for this solution to be viable, is that it would always catch the keyboard input when the screen is opened. So even when the focus is on a different part of the screen, like a detail window or the breadcrum/title bar.It should also distinguish the on-screen keyboard/normal keyboard from the barcode scanner input (with a prefix or time-based). Quick and dirtyAs a quick and dirty solution, would it be possible to add a custom javascript event listener that catches the keyboard input, distinguishes barcode input and calls Indicium to insert a record or execute a tab-task? Something similar as @Jasper wrote here: Upload multiple files using the Universal GUI | Thinkwise Community (thinkwisesoftware.com).

Make table variants user selectable like screen-type / grid variant / graph variant.Merged

I was looking on ways to organize a main subject in an application and this is one of the ideas I got. I will make another Idea for the other option.Business case 1;We have a table with a lot of columns. It would be handy for the user to have a number of predefined sets of columns / views when using the system in different scenarios. Switching on and of columns one by one as is possible now is not really handy with the amount of columns. This is one way to realize this.Business case 2;I don’t find the current option to select the screen type handy as it allows to select default screen types which might not make sense for the application and storing it in the user profile makes that a user could “get lost”, not remembering that he or she is looking at something else then other users. The option also doesn’t allow to configure what screen type is handy where, and where it should be allowed or not.Idea;I think that this idea would improve both, giving the developer the option to create a number of preconfigured configurations, which can involve a large number of settings, including the grid layout and the selected screen type.The developer can make a number of variants “available for user selection”. ( Best specific for “Main view”, “Detail view”, … etc. )   The configuration in IAM gets a setting to allow this option for the user or not and this could be extended to a per subject / variant setting, so that it is possible to configure where the option is available.   The user gets an option; “select variant” in the menu.   And … the developer could get the option to show the different variants the way variants of Pivot tables and Graphs are currently shown to the user. ( Making the variant toggle more prominently visible, and faster to use ).I think that this would be a very handy and flexible addition, giving more control to the developer who is developing the interface, and a really fast switch between different variants designed for different use cases to the user.  ( The selection doesn’t need to be stored in the user profile, as it is only one click, that way the user can’t get lost).

kenterweemeThinkwiser

Task parameter field width: allow maximum width of no. of form columns availableMerged

StatementIn Universal, it should be possible to increase the field width of task parameters to the maximum available width (retrievable from the no. of form columns available).ProblemI have simple task that contains 2 parameters. But since these contain long texts I want these to display extra wide, the width of 2 or 3 form columns for example. I can give my task 3 columns in width with the task setting "No. of columns in form”. However, since I only have 2 parameters, this setting will be ignored and my task parameters will be displayed in 2 columns.Additionally, the standard field width or label width settings in the task parameter settings are also ignored, as the GUI thinks that there is enough space on my screen. For example when I set my task parameter widths to 500px.WorkaroundAs a work around I have now added 3 extra task parameters, read-only, with 0 label width and 0 field width, and have set my 2 relevant parameters "on next tab page”. This gives me the following result: I now have my 2 relevant parameters 3 columns wide, but I also have an extra bar of unnecessary white space at the top and 3 unnecessary parameters. QUESTIONS:How do we model task popup parameters to be wider without all this unnecessary work? Why is the standard task parameter width ignored, even when I explicitly tell the task it should reserve the space for multiple form columns?