Skip to main content

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...

7 years ago

10501

Idea pipeline (top 25)

Filter by idea status

Filter by product

2004 Ideas

Most replies

Most votes

Newest first

André RomijnCaptain

Action analysis in Universal GUIOpen

In the past, when we used the WebGUI, we used the IAM Action Analysis. After switching to the Universal GUI we can't get any data from the Action Analysis in the IAM. For us, as a ISV, it is valuable for us to know how our application is used by our customers and users.

John LunenburgSidekick

Ability to show table tasks on grid lineWorking on it!

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

Xavier de Bondt

Native OpenTelemetry support for IndiciumPlanned

Indicium has supported Azure Application Insights (Blog post 2021) and AWS CloudWatch (Indicium 2022.2.13) for some time.OpenTelemetry would allow Indicium to expose standardized observability telemetry—such as traces, metrics, and logs—without requiring users to send their data to Azure or AWS.Why?Currently, telemetry is only available when sending the data to either Azure Application Insights or AWS Cloudwatch. Local, on-premise and hybrid deployments could benefit from OpenTelemetry support and route this telemetry to a stack such a Grafana, Prometheus, Loki, Tempo or Jaeger.How?To make this concrete, some suggestions for Indicium in order to support OpenTelemetry:Indicium can send telemetry using the OpenTelemetry Protocol (OTLP) An OTLP endpoint can be configured, using gRPC and/or HTTP. These settings can be setup for a Indicium container using specific environment variables (https://docs.thinkwisesoftware.com/docs/deployment/container_registry_indicium#environment-variables) Settings comparable to the Azure Application Insights (https://docs.thinkwisesoftware.com/docs/deployment/aws#log-to-aws-cloudwatch) can be setup for the OTLP endpoint.

PeterKeerisCaptain

Making the Deployment center more advancedNeeds feedback

Modified by moderator:This idea should be changed to making the Deployment center more advanced so you can use one Deployment center installation to maintain your entire Thinkwise platform:The deployment center can check/download updates of all Thinkwise products itself (including the deployment center itself). You can register all your environments (multiple dev/tst/acc/prod) in it. It gives an overview of all your environments x installed TW products in which it shows available updates/hotfixes that are not installed yet (with a button to initiate the process). For hotfixes could also be considered to let you install them from within SF/IAM hotfix screen. Old idea:Please make it possible to download Thinkwise products without Deployment center and Workspace listener in TCP. Currently TCP always adds the Deployment center and Workspace listener to Thinkwise products downloads, even if you are just downloading hotfixes. This make the download unnecessary big/slow (180mb for 2kb hotfixes).

PeterKeerisCaptain

Make clickable grid lookups configurableOpen

Since Universal GUI 2025.2.13 (rc1) fields with ‘Look-up has popup’ will become clickable in the (non-edit-mode) grid to open the lookup. This is a great feature, however not in all cases is this desirable.There can be multiple reasons to use a lookup popup in edit mode to help the user find the right record, but this doesn’t mean that it always adds value to open the lookup in non-edit-mode. Having many lookup fields in a grid can make the grid feel troubled and I also can imagine it could conflict with setting up a double click task on lookup column.So please make it configurable for (non-edit-mode) grids which look-up field are clickable (to differentiate from the edit-mode). For example under Subjects > Components > Grid.

Robert Jan de NieThinkwise blogger

Bring back quicksearchPartially completed

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.

Harm HorstmanSuperhero

Extend "Make child rights available" with option "Process Flows"New

Setting rights on Process Flows are easily forgotten and lead to unexpected behavior. So please add this option to all assign Rights tasks.

Marius KorffCaptain

Workspace Listener for Linux & macOS 🐧Completed

At the moment, there are no plans to create a Workspace Listener for Linux (source).It would be great to not be limited to Windows and have support for automatic opening of your IDE on Linux. Context:Automatic opening of local code files For additional convenience, Windows users can install the new Thinkwise Workspace Listener. This tool automatically opens the selected code file in your preferred IDE when clicking on the pencil icon. The Workspace Listener is optional. Without it, you can still edit and synchronize code locally (provided you use a browser that supports the Filesystem API), but you will need to manually open the files in your IDE. Browsers with File System Access API Chrome & Edge Browsers without File System Access API Safari & Firefox Windows ✅ Automatic syncs ✅ Automatic opening (using the Workspace Listener) ❌ No automatic sync ❌ No automatic opening Local code editing requires manual copy/paste MacOS ✅ Automatic sync ❌ No automatic opening Linux ✅ Automatic sync ❌ No automatic opening

K.BakkenesCaptain

Possibility to review more than just codeWorking on it!

We regularly see expression columns or prefilter with heavy constructs that effect the performance. So it would be nice if we can review expression columns and prefilter just like control procedures. Which would include the following features: · Approve/disapprove prefilters and expression columns · Add comments when disapproving prefilters and expression columns

PeterKeerisCaptain

Branch switching QOL: show branch descriptionNew

With MCP development in the SF, I am working on several user-stories/branches at the same time. So I am switching a lot between them.To make this easier/faster, I would like a small change to the ‘Switch branch’ task so that the branch field has a lookup showing the [branch] - [branch description]. This way I know which branch includes what from just the dropdown (without having to open the popup). Also with the create branch task, it would be nice to have the branch description as input field.

Edwin SaanSidekick

Double click in schedulerNew

In the WIN GUI to trigger a task, for example to add an activity, you had to double click in an empty cell. From some reason in the Universal Schedular the task is already triggered with a single click. Can we change this somehow to a double click.Now everry time a task is added, the task is triggered twice because in the brains of our users the double click triggers this action, resulting in 2 task windows opening up.Really painful for our users.In addition to this, the double click is needed to start the task if you double click on an existing task.Is not logical that for editing a task you need to double click and for adding a task you need to single click. This is for users pretty confusing..

ThijsThinkwiser

Make multiple Search code screens independent, like all other screensOpen

Current behaviorWhen multiple instances of the same screen are open in the Software Factory, they work independently. Search code is the only exception, because its instances share state:Open Search code and search for term X. Open a second Search code screen and search for term Y. Return to the first screen and click Search again.The first screen now shows the results for Y, and its search term has changed to Y.Why this is a problemUsers learn from the rest of the platform that each screen instance keeps its own context. Search code breaks that expectation without any visual indication. A user who opens a second Search code screen to compare results, or to keep an earlier search at hand, silently loses the first one and may act on results they did not ask for. Even if this is intended, from a user's perspective it is indistinguishable from a defect.ProposalMake behavior consistent (orthogonal) across the platform:Preferred: each Search code instance keeps its own state (search term, filters, results), just like other screens. Alternative: if shared state is a deliberate design choice, make it explicit. For example, reuse the existing Search code screen instead of opening a new instance, or clearly indicate that the instances are linked.What matters most is predictability. Either all screen instances are independent or none are, with no silent exception for a single screen.ContextI originally reported this as a bug. It was closed as intended behavior, with the suggestion to submit it as an idea, which is why I am posting it here.

PeterKeerisCaptain

Double click grid to editUnder review

I would like the option in the SF to set a subject to grid edit mode if a users double clicks on a row (optional: clicking on a specific column like with tasks). I know this can be done already with creating a double click task that uses a proces flow to go to grid edit mode. But it gets quite cumbersome when you want to implement this at almost all subjects that use edit in grid in an application, specially in combination with roles.

peter.bongersSidekick

Branch validationsMerged

Create a filter under creation, validations to show only validations that are new in the branch.For example main branch has still 30 open validations, feature branch has 50 open validations. When the filter is active only show the 20 validations.

ThijsThinkwiser

Way to hide all validation messages for a branch at onceOpen

I have created a new branch. Consequently, I inherited 14,060 validation messages from the original branch. Among this vast number, any new validation messages introduced by me are obviously not noticeable. This compromises the quality of the product I am developing.I believe the original branch should be "clean," but in practice, this often proves difficult to achieve. Until that ideal is met, I think it is a good practice to hide all existing validation messages for the branch immediately after creating it so that I can start with a "clean slate."This can be done from SF, but it is a laborious task because:Some validation messages produce an error when trying to hide them, which interrupts the task. Not all validation messages are displayed, as a summary item appears for more than 25 of the same type, requiring manual expansion of each. It involves handling a large number of validation messages.There should be a way to hide all validation messages for the branch at once.

BramGWarrior

Make validations part of the merging processOpen

Hello, we have recently started using the latest version of the SF and are extremely happy with the ease of branching and merging and are trying to ensure stability with unit tests and smoke tests.Currently, a branch can be merged into the trunk without having to do any validation. We would like to make running validations part of the merge process, as is currently done in the upgrade process. At the moment this is already possible of course, but it would be more convenient to see the merge sessions on one screen.Personally, we would at least like to see if there are unfinished/failed unit tests, if there are unfinished/failed smoke tests and if there are control procedures that are still under development/in review.

peter.bongersSidekick

Merging branchesMerged

When creating a merge session a option to validate if all functionality templates are reviewed and not on status development before the merge will be executed, all kind of checks that can be done before executing the merge session (a option to validate) would be nice.

Harm HorstmanSuperhero

Multi line support for Label ControlOpen

We miss the possibility of making Label Control columns multiline.A typical scenario, is a dynamic questionnaire, like belowWe worked around this by means of a read only Multi line text control, which is not ideal

Michelle AudiffredRookie

Paste multiple options in a search bar or filterOpen

Our users need to search for multiple articles or other options in their work, to change statusses of those, or edit other data combined with the selection, therefor they paste a total selection with multiple search terms seperated by a character.They want to search / filter like this: 2508*|2517*|etc… - it can also be with a comma to seperate the keywords, or other regex variants.But now they need to filter for them one by one by one. Which takes a really long time.Can we add the possibility to search or filter on multiple option by filling in the options in one long query or string?

Koen FrankenRookie

Native tag functionalityMerged

We often receive request from users to filter and organize data from different perspectives and dimensions. as responsibilities vary between users. For example, one user may be responsible for purchasing, while another focuses on planning.In addition, we are seeing a growing demand for different types of classifications, both among users and across different business entities. To avoid having to create a dedicated column for every new classification, we would like to provide users with more flexibility with the use of tags. We have noticed that this functionality is available in most modern web applications but is currently not supported in Thinkwise. While it is possible to display tags using an HTML column combined with custom CSS, extending this with functional behavior is not user-friendly. In such a setup, multiple tags (text) are stored and displayed within a single column, meaning that filtering is currently only possible using LIKE operators. This is not ideal from a performance perspective, especially when working with large master data tables. It would be valuable if Thinkwise offered native support for working with tags. This could potentially be achieved through a new domain or control type, allowing tag elements to be created and managed dynamically within the application. In the ideal scenario, users would be able to:Select one or more tags when filtering data. Create new tags directly from a grid or form. Click on tags to instantly apply a filter. Sort and group data based on tags. Manage tags dynamically without requiring database schema changes or additional columns.This functionality would improve usability, flexibility, and scalability, while reducing the need for customizations and additional database columns whenever new classification requirements arise. Example of the current solution using HTML and custom CSS:

Harm HorstmanSuperhero

Multi value Lookup / Tag BoxOpen

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!

PeterKeerisCaptain

Use prefilters as badge codeOpen

In most cases that we use badges, the badge is the number of lines on the screen based on certain active prefilters. If something changes in the definition in one of those prefilters, the developer has to remember to check the badge code and make the equivalent change there.To reduce this maintenance, I would like the option to model a badge as a combination of prefilters on the table/view and that the SF generates the badge code from this.Of course it should still be possible to write own badge code for exemptions.

SabineRookie

Show that a pre-filter is activeOpen

We have pre-filters behind the three dots in a menu.Users are sometimes not aware that pre-filters are active as you cannot see this directly on screen.Is it possible to add some kind of notification or icon to show pre-filters are active?

SabineRookie

Option to rename the form tabOpen

We would like to be able to use a different label for the form tab in different menu's.For example: we would like to rename the form for purchase orders to Purchase order and the form for sales orders to Sales order.I have been told this is only possible by using a different screen type for each screen. We would like the option to use the same screen type, but a different label.

Harm HorstmanSuperhero

Store SAS token expiration date in Application / File Storage SettingsOpen

In the 'File storage locations' tab of Application / General settings, it would be valuable to have an additional column that stores and displays the expiration date of the configured Azure SAS token.The expiration date can be derived directly from the SAS token itself (from the se parameter). Because of this, the field could be populated automatically whenever the SAS token is saved.Additional optionsHighlighting tokens that are nearing expiration Generating notifications for application administrators before expiration occurs Add badge to the tab

Filter by product

All products
Community
Deployment Center
Documentation
Indicium Service Tier
Intelligent Application Manager
Mobile GUI
Software Factory
Thinkstore
UI/UX
Universal UI
Upcycler
Windows GUI
Testwise

Powered by Gainsight

Terms & ConditionsAccessibility statement

Sign up

Already have an account? Login

Login

Login to the Thinkwise Software Community

Login

Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

Enter your email address

Back to overview