Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1910 Ideas

Robert Jan de Nie
Thinkwise blogger
Robert Jan de NieThinkwise blogger

Bring back quicksearchPlanned

In previous iterations of the Thinkwise GUI you could perform an action called quicksearch. How it worked:Bring focus to a specific column (in the grid) Type what you want to search  First match of your search gets selected/highlighted. Can we please have this back?Why Quicksearch is valuable (and missed)1. Strong productivity gain for keyboard usersQuicksearch enabled fast, uninterrupted workflows:No mouse interaction requiredNo modal dialogs or filter configurationImmediate feedback while typingFor users who work with data grids all day, this shaved seconds off every lookup — which adds up quickly.2. Ideal for exploratory and ad‑hoc searchingQuicksearch was perfect when:You don’t know the exact valueYou just want to jump to something that looks rightYou don’t want to define a full filter for a one‑off checkCurrent alternatives (filters, column search fields) feel heavier for this use case.3. Lower cognitive load than filteringQuicksearch required almost no mental overhead:Focus columnTypeFirst match selectedCompared to:Opening filtersChoosing operatorsApplying / clearing filtersThis made it especially useful during conversations with users or while debugging data.4. Excellent for large datasetsIn grids with many rows:Scrolling is inefficientSorting doesn’t always helpFilters can be overkillQuicksearch acted as a “jump to value” mechanism, not a data‑reduction mechanism — a subtly different but very useful interaction.5. Consistency with legacy behavior & muscle memoryMany long‑time Thinkwise users built muscle memory around this feature.Its removal:Breaks established workflowsIncreases friction when moving to Universal UIMakes Universal UI feel like a regression in this specific area, despite its overall improvements6. Complementary, not a replacement, to filteringQuicksearch didn’t replace filters — it complemented them:Filters = structured, intentional selectionQuicksearch = fast navigation and orientationBoth serve different user intents and can coexist.

Arie V
Community Manager
Arie VCommunity Manager

Ability to hide Domain element based on logicOpen

We often have situations (especially on status fields) were a user is only allowed to use certain element values or to move it from one element to one other element. The availability of a given element would be based on User permissions or current status (for example: if current status is A, you can only change it to B, and if current status is B you can only change to A or C, but not D). The current ways of resolving these situations feel like workarounds, which should not be necessary for such a straightforward request in a platform called low code. Suggested solutions I have heard are:Create two (or more) similar Domains with similar, but not all, Elements and determine in the Layout procedure which one to show. This basically means adding (sort of) duplicate domains, which is ugly and risky from a maintenance perspective... Use a Lookup to a Table or View with Pre-filters. This is more effort, clutters the Data Model and is probably worse in performance than a Domain with Elements...A possible solution that comes to mind is the ability to set in the Layout procedure when to show/hide certain Elements. It would be good enough if somehow the Layout procedure recognizes Domain with Element type of fields and we can write logic on each individual Element within that Domain.  How do you like this idea? If you have other suggestions than the Layout procedure to fix this: let's hear it!

Navigation sidebar - Improve menu-item openingOpen

There are currently 4 ways to open a menu item from the navigation sidebar. User opens a menu-item by CLICK or keyboard-select/ENTER. This opens the menu item in the current browser tab. This is correct behavior (no changes proposed). User opens a menu-item by ALT+CLICK or keyboard-select/ALT+ENTER. This opens the menu item as a new browser window. The following improvements are suggested:The new browser window misses parts of the browser topbar (it shows URL bar only). Improvement: open as a regular browser window. The navigation sidebar is missing in the new browser window. Improvement: open the browser window with the navigation sidebar visible ALT is not the universal browser convention to open links in a new browser window. Change this to SHIFT. User opens a menu-item by CTRL+ALT+CLICK or keyboard-select/CTRL+ALT+ENTER. This opens the menu item as a new browser tab. The following improvements are suggested:The navigation sidebar is missing in the new browser tab. Improvement: open the browser window with the navigation sidebar visible CTRL + ALT is not the universal browser convention to open links in a new browser tab. Change this to CTRL (also: scroll wheel click). User opens a menu-item by SHIFT+CLICK or keyboard-select/SHIFT+ENTER. This opens the menu item as a near-full screen focused pop-up. The following improvement is suggested:SHIFT should not be used for this as that is the universal browser convention to open links in a new browser window. Change this to CTRL +ALT (or another combination that does not interfere with standard browser conventions). Note 1: all above is described from a generic Windows desktop user perspective. Thinkwise to align this to Apple and Android OS’es as needed. Note 2: the browser context menu when right-clicking on a menu-item should also include default options such as ‘Open link in new tab’, ‘Open link in new window’, etc. It currently does not show that.

SanderAdam
Captain
SanderAdamCaptain

Single click tasks for card lists on mobile devicesOpen

Hello all,We have a scenario where we want the user to navigate to a details tab, the user in this case is on a mobile device. While on a tablet, there are some options to make a detail tab appear on the side of the screen, this option is not doable for mobile phones. And some of our users are going to use mobile phones instead of tablets.We used a task link before, so the user can click on a task on a record, but this is not ideal. This is not the web and mobile way. As Nielsen and Norman's 10 usability heuristics put it: recognition rather than recall. On mobile and web applications (looking at apps like Outlook and Gmail) it is common to have a single click on a record. Just on the record, not on a task button integrated in the record.A user will recognise a single click on a card record to navigate to the details, rather than having to actively push an integrated button, link or a double click. This is all very Windows oriented and not quite how web and mobile apps are built. We find it to be inconsistent with web standards. So that is why I would like to request a single click option: as single click on a card record, like in Outlook or Gmail to get to a detail view of a said record via a task and (if necessary) process flow.Though I've seen merged ideas to the following idea: https://community.thinkwisesoftware.com/ideas/ability%2Dto%2Dshow%2Dtable%2Dtasks%2Don%2Dgrid%2Dline%2D518 This is not what we are looking for. This is still a new feature which is very Windows oriented. We don't want extra buttons in our records, we want the user to just click a record once and navigate to the desired details.This happens to fall nicely under the fourth Nielsen and Norman usability heuristic as well as the sixth:Consistency and StandardsUsers should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.Jakob's Law states that people spend most of their time using digital products other than yours. Users’ experiences with those other products set their expectations. Failing to maintain consistency may increase the users' cognitive load by forcing them to learn something new.Recognition Rather than RecallMinimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.Humans have limited short-term memories. Interfaces that promote recognition reduce the amount of cognitive effort required from users.At this point in time, we have quite a history of user actions on the internet, and the single click on a card record (like in Outlook or Gmail) is one of them. This would, instead of a new double click action, greatly increase usability of our software, especially for those that are not too well versed in computers and mobile devices.