Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
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.
Sharing functionality for TCP contactsToday I wanted to easily share a contact from the TCP application with a colleague, but there is currently no direct way to do so. In modern applications, the ability to quickly and securely share information is considered a standard feature.Therefore, I propose adding a user-friendly sharing option, for example via a deeplink. This would allow users to share relevant information with colleagues or other authorized users in just one click.Why this adds value:Improves efficiency and collaboration between users Aligns with expectations of modern software Saves time and eliminates the need for manual retyping or screenshots Can be implemented securely based on access rightsIn short: a relatively small enhancement with a significant impact on usability and productivity.
In the Universal GUI we are missing tooltips in radio buttons options. It would be nice if we could translate options as abbreviations and see the translated tooltip when hovering over the option itself. In the print screen below you can see that Fresh produce uses its default translation as a tooltip (because it is too long). CU can not be shown as a tooltip yet.
Some mouse clicks less by simply combining Save and Select in one button in Lookup forms
It would be great to have a way to automatically generate certain roles. For example, by using AI. Creating roles is quite a lot of work and something that often results in minor mistakes. Some how it feels kind of strange that there is no way to get some roles for free. Without having to do any work.I think that it can, and should be, possible to generate certain roles and therefor get these for free. Like get a read only and a management role for each menu entry.The read only role has access to the subject and all the visible details, but only ready only access.The management role has access to a subject and all the visible details. This role also has access to all the prefilters, tasks, reports and can insert, edit and delete on all these subjects.Having these roles available will save up quite some time. Since around 80% of your roles you will need is a management and read only role per menu entry.This might seem like a lot of work, but it could already be created through the enrichments. And with the coming of a MCP layer that should that simpler to implement.
We often get requests from our business to show a popup form when adding a new record instead of going to a form tab (or have an always shown form below a list). This is a behaviour that is present in many other systems. This is currently done by creating a tasks that shows the same fields as the form, a lot of duplicate, extra, work and lots of places for new bugs to be introduced (rights, defaults, layouts etc etc).Would be nice if we can just select the flow that happens when creating a new recordsCurrent behaviour (default) Show popup formMaybe even support this when doing edit etc.
After my presentation at the Thinkwise Developer event 2026 about the use of a Form popup to mutate data a lot of feedback was given that such a method should be a default option. So let’s make it an official idea!Idea: Give us an option to make the Create / Update action show us a Form popup by defaultFeel free to comment suggestions of how you think it should work, but here a few that were discussed or mentioned to me.When no form present, popup with the form instead; Bullet 1, but with added config. Choose a variant for each action (Create, Update). Same table/view.; Bullet 1, but with added config. Choose a target detail through the appropriate reference. So possibly a different table/view.Also credit to all the people for complimenting this idea!
As a developer, I want the “Database event log” readability to be improved.At the moment, the queries in those logs are not structured enough:Original topic text:On debugging I use the debug information/pane all the time and I’m pretty sure I’m not the only one.Really important information in this debug pane is the content of the form parameters and f.e. the task parameters. If these are lookups we can see the ID’s of the related tables there.As far as I can see now there is no way to view this info in the Universal GUI. That’s huge ommission when developing and it holds me back from developing in the Universal GUI. You’re working a kind in the blind… Hopefully I missed something in the documentation (However I’ve searching for about an hour) but this really important information should be visible as debug info in the Universal GUI. I’m a functional developer so I need values of the data being displayed and the underlying ID’s of related tables. In many cases issues in applications are data related!!!!
The thinkwise platform is very powerful as it comes to referencing information and one of the results is that the screen gets bloated with tabs up till the point there are just too much. The fact that you can have horizontal and vertical tabs is already great. However I would like to be able to group tabs to deal with larger tab-lists and references that functionally can be grouped for better understanding by the user.Like below, where there can be maybe a left-border color for the status references or just some white-space between the status-group (first-four reference) and the other ones. I guess a bit like the pre-filter, task and report groupings.
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!
Unfortunately, it is still not possible to subscribe to receive notifications for new arrivals, so good ideas can easily be missed and forgotten.I was thinking of a possible workaround, as long as GainSight can't provide a solution...Is it not possible to build a workaround within the capabilities of Thinkwise and have an overview of new ideas sent weekly from TCP to notify all users with a Thinkwise account?Download ideas with HTTP Connector, etc...https://community.thinkwisesoftware.com/ideas/topics?page=55&sort=%7B%22createdAt%22%7DSee also:
We’ve used the Redgate SQL formatting (also mentioned here SQL-code formatting guidelines renewed | Thinkwise Community) in Azure Data Studio for a while. As of february 28 2026, Azure Data Studio is retired, so we’ve moved back to SSMS.Recently, Redgate has disabled the free use of this tool.It would be great to implement a similar feature into the Software Factory or the Workspace Listener.Redgate uses JSON to setup the preferred formatting style. Perhaps a similar system (either JSON or a table in the SF) can be implemented where the Thinkwise formatting guidelines are setup as default formatting.
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.
When a look-up control is set to suggestion, the dropdown of the lookup only shows the first 8 results. But in fact there could be a lot more results. This is not clear to the user. Please add a visual indication for the user when there are more results. Preferably when clicking on the indication, it opens the lookup popup.
A request I heard a lot from users over the years is to make it possible to select multiple rows in a lookup window and add them all at once. I don’t see a reason why it shouldn’t be possible if we accept the following limitations:The user must be adding a row (not editing). All fields (excepts for the lookup field) must be optional or filled with a default value. So no user interaction is required to add the row. Although maybe it could be possible to allow mandatory fields that are not filled with a default procedure if the user just enters it in the first row and the same value is used for all rows. So if the user wants to add multiple rows, he presses the ‘Add’ button, opens the lookup window and select multiple rows. The GUI should fill in the first row, save the row, automatically add the next row with the next selected value and continue this until all selected values are added. The default/layout procedure should be executed for each row. If one rows encounters a problem, for example one selected value is rejected in the default procedure, It should skip that row and continue with the next one. A same kind of summary popup with failed rows could be shown to the user as is done with the mass-update feature.
Please add a more simple way for end users to assign more than 1 value from a source table to a target table.Like this:It will make screens less more complicated for end users and will increase the adoption of new applications.Must not be missing in a modern application!
I often have trouble finding the right icon. It would be great if I can describe the icon I want and have the Software Factory (using gen. AI) create an icon for me. Perhaps, as context, I should have a place where I can store the project guidelines for icon usage, for example colour usage, complexity, etc. This way, I get a more predictable outcome for the icon.In my mind the context given to the AI should be as follows: Object type (task, prefilter, table, etc.) Object name Object translation Object description (application specific) guidelines regarding icons Some sample icons coming from the current set Optional description of what I wantThe output should be a proposed icon (svg) that I can either: Accept and use Reply to and ask to generate a new icon
When the Global search field is shown as a button (without the text field), please make a visual indication when a search criteria is entered.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK