Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
We would like a new control type that allows users to easily select an amount of time (hours and minutes) and store this data in our database. This could be a decimal format where 65,75 is displayed in the UI as 65:45. The currently available control type TIME is used to store the time of day. It cannot be used to select or display an amount of hours and minutes exceeding 23:59:59.
We would like to have the ability to show table tasks on a grid line. This is especially useful for the mobile GUI and when just a couple of table tasks are available. Currently you can show tasks on the top or bottom of a grid in mobile. To start a task for a specific record you should select a line first and then select the concerning task. In the described case it is faster to select the task direct on the line. See print screens for further explanation. Task on top of grid (current situation) Example tasks on grid line
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.
I would like to see import from clipboard for the universal.
Currently, the Software Factory (SF) maintains the selected model/branch at a global session level within the browser. When a developer needs to work on or reference multiple models, they have to manually switch models. Switching models automatically closes all currently open tabs and windows within the SF, and I think that is logically but It is impossible to keep two different models open in separate browser tabs or windows to compare configurations. And yes, I know this is possible with another browser or an incognito, but I think there is a more convenient way.So it would be helpfull if it it possible to allowing developers to open multiple models or branches simultaneously in different browser tabs.
The SF and data domains offer little possibilities to control the presentation of numbers. I thought the custom_display_format extenders would be the solution but I found some shortcomings that make them less useable in practice. I discussed this with Thinkwise people: The current behaviour is as intended but they think the following would be a good improvement.Simple example for a currency datatype NUMERIC(18,3) where users normally want to see only 2 decimals but the extra decimal is needed for calculation accuracy. By using an extender with "€ 0.00" format for the domain you get the following behaviourPositive:Display with 2 decimals is correct and third decimal is used for rounding up/down correctly An entered number with 3 decimals is correctly stored in the underlying tableNegative:When EDITING data there is no way to see the third stored decimal When EDITING it is not possible to edit the existing number; you have to clear the field and reenter the complete numberThe behaviour is the same in grid and form screens. We would expect behaviour like e.g. Excel:Display data using the Extender. They are called custom_display_format for a reason I think. Possibility to edit the exact stored dataWithout this behaviour the introduction of the extender seems of little use; the same could be achieved using an expressions field. But a task would be required to edit data and this is what we want to prevent.An extra improvement would be if the scope of the extender could be specified on a lower level than a domain. Then you would get the possibility to present and edit the same table field in multiple ways; the exact data for the finance department and in another screen rounded numbers for sales but still the possibility to edit the exact number.
It would be nice to have a variant_id for layout , context and default
We utilize variants extensively in our platform as this is one of the powerful benefits of Thinkwise. However we encounter pretty often that we want to build tasks and even layouts that should behave slightly different based on what variant they are opened/used from. Currently there is no real neat way of having that information available in the code/flow so we often have to resort to, in our opinion, janky solutions. If its possible to add the current variant as input parameter this would open many doors and possibilities.
I have a view with 3 fields that can be automatically filled (default proc) when selecting one value from a view having all three values concatenated.This makes finding things a lot easier for the user. The field is only defined in the view and nothing is stored in the database…. A similar situation now exists in a table. There is currently no need for a view instead of this table, so an expression field could be the solution here. Expression fields in the SF however are by definition read-only. So why not have the developer deside whether an expression field is read-only or not; most of us are wise enough to know what we're doing. To show what I mean, see link below… I made an expression field editable using SQL on the SF database, and you;ll see what I want to achieve. Works fine according to me. https://mcmurdock.stackstorage.com/s/4pGhtJXw03Y9EH8
Sometimes there are things that are linked to a variety of subjects, like relationship that are linked to objects or object_parts or contracts. Now I have a subject in which I want to use a relationship, but sometimes I would like to add a relationship that is linked to an object and sometimes I want to add a relationship that is linked to a contract. I thought I might use a variant that uses a lookup for relationship for objects in one instant and a lookup for relationships for contracts in the other instant. However the lookup of a variant cannot change and is always the same as was specified in the default. I would like to be able to assign a different lookup table to a variant.
Could you make an adjustment to the barcode control to enable committing with Enter, since the Tab key is not present on the on-screen keyboard of mobile devices?
I would like to be able to go to a row in the grid based on what I’m typing and the value of the selected column in the grid. (quick search?)The reason for this would be to save users the action of having to go to the search bar (which currently still requires the mouse, we would liek it to be keyboard only) and having to wait for the results to be retrieved again, even though the relevant data was already retrieved, it just wasn’t selected.This was a feature in the Windows GUI and it would be great to have this again in Universal, perhaps with some highlighting of the typed characters in the resultMy use case for this is order entry, when selecting order lines from a list of relevant products
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.
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