Product updates
Ideas
Events
E-learning
Documentation
TCP

Create a new topic
Login

Ideas

Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.

Featured Topics

F.A.Q.

What happens to your ideas?

Your input is very valuable to us. That is why you can share your ideas for improving the Thinkwise Platform. (Last updated: november 2024)Tip 💡Don't

Forum|Forum|6 years ago

9991

Idea pipeline (top 25)

1862 Ideas

Newest first

Most replies

Most votes

Robert Jan de NieThinkwise blogger

Reorder favourite screens on loginNew

Universal UI allows you to mark screens as favourites and automatically open them on login, which is great.However, the order in which favourite screens open cannot be changed.They always open in a fixed sequence.Why this mattersOften, I want:Context screens (overview, dashboards) to open first My main working screen to open last, so it has focus and I can start working immediatelyRight now, I need to manually switch tabs every time I log in.ProposalAllow users to reorder their favourite screens, so the login sequence matches their personal workflow.This would be a small UX improvement with a noticeable productivity benefit, especially for users who log in frequently and work from a primary screen most of the day.

0

Forum|Forum|1 day ago

Robert Jan de NieThinkwise blogger

Non‑numeric visual indicators for tabs and menu itemsNew

Currently, we allow numeric badges on tab pages and menu items. This works well for counts (e.g. number of records, open tasks).However, there are many situations where a number is not the right signal, but the user should still be visually alerted.The limitation of numeric badgesNumeric badges implicitly communicate:Quantity Work to be done BacklogBut sometimes the intent is different:“Something needs attention” “There is uncertainty or missing information” “This section contains an exception or warning”Using a number in those cases:Adds unnecessary cognitive load (“what does this number mean?”) Can be misleading (“do I really have 1 thing to do?”) Trains users to ignore badges if they are often not actionableProposal: Support symbolic / icon‑based indicatorsAllow tab pages and menu items to display non‑numeric indicators, such as:⚠️ Exclamation mark (attention required) ❓ Question mark (incomplete / unclear data) ⛔ Error icon (invalid or blocking state) ✅ Check icon (explicitly OK / completed) ● Dot indicator (something changed)These indicators would be data‑driven, just like numeric badges today.Why this is valuable1. Better alignment with user intentIcons communicate state, not quantity.This matches many real‑world business scenarios better than numbers.Examples:A tab contains inconsistent data → ⚠️ Required fields are missing → ❓ Validation failed → ⛔ Approval completed → ✅2. Faster visual scanningUsers don’t read numbers — they scan for patterns.Icons:Are recognized instantly Reduce interpretation time Draw attention without demanding actionThis is especially effective in:Complex screens with many tabs Role‑based applications where users need guidance Review or exception‑driven workflows3. Prevents notification fatigueNumeric badges can feel like “todo counters”. When everything shows a number, users start ignoring them.Symbolic indicators:Feel lighter Communicate importance, not volume Are less stressful and more selective4. Improves guidance without extra UIThis approach:Avoids adding extra columns, banners or messages Keeps the UI clean Uses existing UI real estate more effectivelyIt’s a low‑visual‑noise, high‑signal improvement.5. Backward compatible and complementaryThis would not replace numeric badges, but complement them:Numbers → “how many” Icons → “what kind of state”Developers choose the most appropriate signal per use case.Example use cases Customer screen “Details” tab → ✅ “Contracts” tab → ⚠️ (expired contract) “Documents” tab → ❓ (missing upload) Workflow‑driven application Menu item “Review” → ● (new activity) Menu item “Errors” → ⛔ (blocking issues) Master‑detail screens Child tab highlights issues without forcing users to open each tab Optional implementation direction (high‑level)Allow badge type to be: Numeric Domain with elements and Icon Icon visibility driven by badge logic / domain value Optional tooltip to explain the meaning

2

M

Forum|Forum|1 day ago

Robert Jan de NieThinkwise blogger

Bring back quicksearchNew

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.

0

Forum|Forum|1 day ago

Arie VCommunity Manager

Activate top-left Screen Component upon opening a screenPlanned

Upon opening a new Document in the Universal GUI the first value in the top left (at least for Western writing) Screen Component should be activated. This especially goes for the Grid component, where it seems as if the first Row is selected. In below example it took me 44 tabs to get to the first column value of the seemingly selected Row. Could the Universal GUI be a bit smarter here?

4

Forum|Forum|1 day ago

Harm HorstmanSuperhero

Show barcode keyboard buttonCompleted

We have deployed an application for use on a ZEBRA scanner device.The application functions smoothly and intuitively, with one exception.It is designed around barcode scanning, and in over 95% of cases, the process can be completed simply by scanning barcodes. To support this workflow, the SuppressBarcodeKeyboard setting is enabled (Yes), which hides the on-screen keyboard.However, this has a side effect: users are unable to manually enter codes using the keyboard. This becomes problematic when barcodes are either inaccessible to the scanner or damaged.To address this, we would like to add an action button within the barcode control that allows users to activate the keyboard when needed.Something like this:We hope this is possible.Alternatively, is there another workaround you would recommend?

7

Forum|Forum|1 day ago

M

Mark_PlaggenborgSuperhero

Make "Close document" a possible starting point in a process flowCompleted

We use a lot of Modal document form in our application, which works great. There are however some situation where a process flow end with the opened document. After a user is done with the required actions we sometimes desire to take care of certain actions after or triggered by a closing of the document.Unfortunately this Action does not count as a starting point.A workaround for now is using a task in the screen that follows with a “Close document”, but the user often misses that. The “CLOSE’ button takes so much focus, that such a task would be missed. Also if the screen already has many tasks, it would not stand out that much anyway even when marked as primary. The idea is to make “Close document” a starting action in a process flow.The idea of course goes with a warning that the “Close” is always available on such a document, that one should be aware it could be pressed without actively having done anything in the screen and uses it as a cancel, but I think this should be the responsibility of the developer using such flows.

9

Forum|Forum|1 day ago

FreddyThinkwise Local Partner Brasil

Import from clipboard - UniversalWorking on it!

I would like to see import from clipboard for the universal.

7

Forum|Forum|1 day ago

A

avanderveldenVanguard

User preferences - set Start Objects in UniversalWorking on it!

Can the configuration under User Preferences to set Start Objects also be made available in the Universal GUI, as it is in the Windows GUI?

9

Forum|Forum|2 days ago

J

JeanPaulRookie

Some improvements on visibility of open documentsWorking on it!

In the universal GUI opening (a lot of) documents can make the navigation panel cluttered and even push the menu out of sight: Some suggestions to improve this: Split the navigation panel in two panels with seperate vertical scroll-bars as soon as the number of open documents exceeds a certain treshold Add levels for detail-documents beneath open documents and collaps them the same as the menu tree with (automatic) collapsing and expanding Add context (part of the breadcrumb) to the title or mouse-over of detail-documents to prevent having to open a document to see wich one is the right one Another suggestion: An option to lock an open document, so that it is available the next time I login to the application

14

Forum|Forum|2 days ago

J

jkruterVanguard

Context parameters for badgesDeclined

As an alternative for this idea: Some improvements on visibility of open documents | Thinkwise CommunityI thought I might be able to use a badge to achieve the same result. I looked very promising, until I realized badges only know the context of the possible parent relations, not the subject itself (other than @variant_id).If we had access to the subject’s context, like the selected row’s primary keys, or the column filters (set by the “Change filters” process action), badges could be much more versatile.

5

Forum|Forum|3 days ago

Marius KorffCaptain

Context menu (Right-click) support for Universal GUIOn the backlog

Being able to right-click on rows would enhance the user experience a lot!Basically the same idea as what is currently working in the Windows GUI:

10

Forum|Forum|3 days ago

E

Erwin Ekkel

Untranslated option for universal guiOpen

In the windows gui you had the option to show the application without any translations. This functionality is missing from universal. For debugging purposes I would very much like this option to return. When I investigate a problem on an environment I don’t know I have to use the translated object, translate this to the database object. Then revert this to get the menu objects I need. I know application insights is a thing. But that doesn’t always work and is still not as fast as just showing the application without translation used to be.

2

Forum|Forum|3 days ago

htimmermansCaptain

Disable translation in Universal GUIMerged

In the Windows GUI a developer could choose to disable translations of domains and fields. This comes in as very handy when one wants to see which field is shown in, for example, a form. In my case, depending on what box is checked, a field called supplier_no is shown or homedealer_supplier_no: Switching on / off for translations in Windows GUI: I have not yet found the same functionality in the Universal GUI. Perhaps something to support in the future?

1

Forum|Forum|3 days ago

C. LousbergCaptain

Login-option based on network-locationOpen

it would be great if Universal GUI/Indicium can determine if the user is on the local network or somewhere ‘outside’.In case we can determine the inside or outside location, it should be possible to configure the “login verification” at the user (or maybe application ?) per location.E.g.LAN login verification: “Password” Non-LAN login verification: “Password and TOTP token”This will make it possible to setup MFA for external usage, and avoid the additional factor in case working on the LAN.

3

Forum|Forum|3 days ago

P

PeterKeerisCaptain

Multiple selected row + edit button = mass updateNew

The mass-update button is a bit hidden behind the three-dot button. Could the Edit button react based on how many rows are selected? So if you have one row selected and press the Edit button you get the current behaviour, but if you have multiple rows selected and press the Edit button it opens the mass-update popup.

0

P

Forum|Forum|8 days ago

Harm HorstmanSuperhero

Execute Hotfixes from inside IAM/SFOn the backlog

Can you please add an option to execute hotfixes from inside the hotfix screen, without the need of download and install a installation package.

4

Forum|Forum|8 days ago

E

Erwin Ekkel

Make IAM great again: redesign screens to use less detailsCompleted

Now that customer success is the focus. Can we also put some love and care into IAM? A lot of the screens are loaded with detail upon detail upon detail. Here is a small snippet of one of these monstrosities. Working on a laptop screen using Iam is next to impossible. Using less details and maybe aggregate some information into 1 view instead of a lot of details would greatly benefit the useability. Or add AI so I can ask IAM if a certain user has access to a certain menu sub item.

12

Forum|Forum|8 days ago

H

Henno TillemaRookie

Extend custom_display_format functionality to get Excel like field display/edit possibilitiesOn the backlog

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.

3

Forum|Forum|8 days ago

Harm HorstmanSuperhero

Simplify use of Refresh Model task during developmentPlanned

During development, the "Refresh Model" task may be called hundreds of times per day.It might be an idea to move the task to the header bar or assign a Shortkey to the task.And at the same time ignore all warnings, because they do not matter during development. This will definitely save a lot of time during development.

8

Forum|Forum|8 days ago

E

Erwin Ekkel

Make Launch Application also perform a refresh modelPlanned

The launch application option in 2026.1 does not do a full refresh model.I’m not sure what it does exactly but it seems to load the menu and screen but not the new data model. I would opt to always perform a full refresh model when using launch application. Since you want to see the application in it’s current state, not in some half cached state.

3

Forum|Forum|8 days ago

P

PeterKeerisCaptain

Look-up dropdown - indication when there are more optionsNew

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.

0

P

Forum|Forum|8 days ago

P

PeterKeerisCaptain

Adding multiple rows at once through a lookupNew

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.

0

P

Forum|Forum|8 days ago

Robert Jan de NieThinkwise blogger

Create icon using AINew

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

0

Forum|Forum|10 days ago

B

BjinseApprentice

Make it possible to disable autocorrect for (search) fieldsNew

When using the Universal GUI in Mac OS Safari, the fact that all edit fields use autocorrect by default, is very annoying. For example, when searching for a partial customer name, at one time you see the you typed enough characters to find the record you want. When you then navigate away from the search field, autocorrect kicks in, and often the autocorrected partial name is not what you want. Then the grid is empty or at least changed.As far as I see, this only happens in Safari, because Chrome does not have autocorrect.It seems disabling autocorrect is only possible / necessary in Safari and Firefox: https://caniuse.com/?search=autocorrect Being able to also disable autocorrect for form fields and grid fields could also be a handy feature. But there it could probably default to autocorrect=on for most text fields.

0

B

Forum|Forum|11 days ago

M

MaartenWarrior

Optimize the smoke test screenOpen

In the smoke test screen you are quite limited on functions. I would love to see 2 things added here.A Task to hide a Test, or approve. Just like in the validation screen. Take for example a View that command timed out. You know the reason but it still pops up in your list and give alot of cluther arround the test steps that matter. Another great task which is introduced in a lot of screens is the Go to functionality button or Go to prefilter button. Currently when something is wrong with a prefilter in the test step, you are not able to edited it in the form. You need to open it separately in subjects. Or when something is wrong with a view I would to go to the view code directly.

2

R

Forum|Forum|11 days ago