Skip to main content

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

Idea pipeline (top 25)

Filter by idea status

Filter by product

1986 Ideas

tiago
Captain
tiagoCaptain

Navigation buttons "previous" "next" for detailsOpen

A use case that happens ins many cases is where you have the grid with a detail tab with the form and other elements. For the user It's quite cumbersome to be going back and forth every time he wants to see the details of a couple of items in a row. I really miss the previous and next navigation buttons in the detail, where you can jump easily to the next or previous item in the context without the need to go back. 

5
Arie V
Forum|Forum|6 hours ago
Warrior
avanderveldenWarrior

Option to set (own) prefilters default onOpen

Via the Windows GUI it was possible to create onw prefilters, which were on “by default” (if on at last use, then these were on next time view was opened).Would be fine to have this option available again 

4
Erik Brink
Forum|Forum|8 hours ago
Robert Jan de Nie
Thinkwise blogger
Robert Jan de NieThinkwise blogger

Make Software Factory metadata available to AI so I can generate SQL templates from my IDEOpen

I want to use generative AI to draft the bulk of my SQL templates, directly from my own IDE (e.g., VS Code) together with tools like GitHub Copilot. For this to work reliably, the AI needs first-class context from the Thinkwise Software Factory (SF): the application’s model metadata and relevant UI information. The SF already maintains a rich, structured model of tables, columns, and references; exposing that to the AI is the missing piece.Why this metadata is essential for AI-assisted SQL When the AI understands my model, its output stops being generic and becomes project-specific:Tables, columns, PK/FKs – enable correct JOINs, WHERE clauses, and integrity-awareness. The SF’s data model explicitly defines these entities and relations, which the AI can use to pick the right join keys, respect cardinalities, and avoid hallucinated columns. Domains (user-defined data types) – domains act as abstract data types that drive constraints and UI defaults. Sharing domains helps the AI choose correct data types, casts, default values, and validation logic in generated SQL. UI semantics – properties like control type or visibility can guide the AI to prefer filtered queries (e.g., hide inactive rows by default) or to shape parameter prompts and WHERE clauses that match what end-users actually see. Template description & intent – short, descriptive text per template (purpose, invariants, edge cases) gives the AI the business intent it needs to generate more accurate and consistent code.How I propose to make this work Expose a compact model export for use in VS Code MVP scope: tables, columns (incl. nullability), primary keys, foreign keys, domains (name, base type, constraints). Optional scope: UI hints (visibility, control), default filters, and template descriptions. Delivery options (any of these would work): Indicium OData endpoint that surfaces a read-only view of the SF model (Indicium already provides an open API and can expose SF branches when configured). CLI/export task that writes JSON files into a repository (consumed by VS Code). VS Code extension that authenticates to the endpoint and injects the model as inline context for Copilot prompts. Use the model export as AI context in the IDE In VS Code, I want to select a template and have the AI read the JSON/endpoint to generate the initial SQL ready for review and refinement. Expected resultsSpeed: AI drafts 70–90% of the SQL, I focus on edge cases. Quality: Consistent use of keys, domains, and defaults; fewer “missing join” or “wrong column” errors. Discoverability: As Thinkwise continues to add AI-powered features (e.g., model enrichments and support for storing LLM embeddings), a model-aware export aligns with that trajectory. Future fit: Community use cases already show value in combining Thinkwise models with LLMs (e.g., natural-language search using embeddings), reinforcing the need for structured model access. 

3
Mark Jongeling
Forum|Forum|4 days ago
Xavier de Bondt
Sidekick
Xavier de Bondt

Webdomain: Allow / disallow applicationsNew

The introduction of the Webdomain has given the possibility to give a different login experience based on the domain.We can allow certain tenants on domains and give them specific login methods to login.What's missing?We still miss the option of allowing / disallowing a certain application on a webdomain.In our scenario, we have two applications hosted on the same IAM/Indicium/Universal combo.It would be great that we could create two webdomains where app-1.mydomain.nl only allows the users to acces app-1 and app-2.mydomain.nl only allows the users to access app-2.Why?Especially in production environments, the switching between applications has to be done right, without question. Switching inside the same Universal GUI instance (say browser tab or PWA), can be tricky, especially when the look and feel of both applications are the same.When allowing the Webdomain to allow / disallow the applications, you could create a PWA for each application easily.

0
Xavier de Bondt
Sidekick
Forum|Forum|4 days ago
Captain
PeterKeerisCaptain

Add menu subtitles support in SFNew

Now I am used to subtitles in my own applications, I am really missing them in the SF.Specially for:-Data model (Tables)-Subjects-Functionality-Tasks-Process flowsCould some workaround be made to support subtitles in the SF please?

0
Captain
Forum|Forum|4 days ago
Captain
PeterKeerisCaptain

Configure 'Search' fields as a user-preferenceNew

The global search is often configured to the most used fields. However this doesn’t always match all use cases. As a user I would like the option to configure this myself on certain subjects. I would like to have at least the option to exclude certain search fields as configured in the model. But preferably also have the option to add other search fields.

0
Captain
Forum|Forum|4 days ago
Harm Horstman
Superhero
Harm HorstmanSuperhero

Max/Min Width Settings for Form-, Task- and Report FieldsOpen

We like to have more control over field widths, because often you wish to give fields a absolute widthExamples:house number postal code dates bank accounts etc..When fields are on the same line it can have a mix of fixed and flexible widths.It should be more easy to set this up in the Software Factory.         

10
Harm Horstman
Superhero
Forum|Forum|4 days ago
Rookie
Michelle AudiffredRookie

Load on scroll instead of paginationNew

When there is a lot of data needed in a view / screen. It takes a lot of performance to load everything all at the same. Sometimes we need to load 50.000 rows or items or lines.To make sure the performance is okay, we use pagination in our grids. So we only load everything per page.Use case: our users need to select multiple rows / items over several pages, but when you go to the new page, it loses the selection of the previous page. Which causes inefficiency for them to execute tasks over several pages.Our proposed solution:Load on scroll. You still can load chunks of data instead of everything all at the same, but you start loading a new chunk ones you hit a scroll depth. Used frequently in webshops to load products on product listing pages.

0
Rookie
Forum|Forum|5 days ago
Moderator
Erwin Ekkel

Code Search more options for debuggingNew

Code search is a great tool, but it gives too much results. For debugging a problem in a live application a lot of the results are irrelevant. Most time i only want to see task templates, triggers and procedure templates. To find which task/trigger etc affects a certain table. My suggestion would be:add a checkbox: exclude non-assigned templates (active by default)add a checkbox: exclude gui templates (this only shows code that would impact results, so only templates for tasks, procedures, subroutines, triggers (i might forget one here?) 

1
Jeroen van den Belt
Forum|Forum|6 days ago
Sidekick
Edwin SaanSidekick

Ability to configure selected rows colorNew

As discussed in topic:Also the users of my clients are requesting for more contrast between the selection and the non selected lines.It would be great if we can have some impact on this. A css solution is also acceptable, not ideal.

7
Sidekick
Forum|Forum|7 days ago
Sidekick
Spyros.NeofytouSidekick

Quick button to take you directly to "Search"Working on it!

Be able to assign a quick button to take you directly to "Search". For example assign "F1" button, when pressed,  to take you to "Search"

6
Arie V
Forum|Forum|10 days ago
Captain
PeterKeerisCaptain

Feedback regarding the new ticket layout in TCPWorking on it!

Good improvement that tickets which require user action are only counted for the badge now and are default sorted on top.   Please add the ‘Product’ field (Universal/SF/IAM/etc.) back to the grid, this helps with finding an issue when you don’t remember the title.   After executing the ‘Annulering beoordelen’ task, an issue stays visible with status ‘Opgelost’ while the prefilter ‘Gesloten tickets verbergen’ is active. For example ticket 14568i.   ‘Activiteit’ and ‘Commentaar’ are a bit confusing/redundant: In ‘Activiteit’ I see the whole conversation, but the Add button doesn’t work (all fields are read-only/hidden). My expectation was that I could add a ‘Commentaar’ line here. In ‘Commentaar’ I only see a small part of the conversation. For example messages that are written when the issues switches status between 'In behandeling' and 'Reactie gewenst' are missing.   The default screentype could be improved if it shows the form below/next to the grid. So you could see the ‘Toelichting’ when browsing through the issues without extra clicking. I am currently using the Master-detail screentype myself. If this is changed, a bit smaller grid height would be appreciated too.   When I use the ‘Kopieren’ button to create a new ticket, I cannot edit the ‘Toelichting’.

7
Forum|Forum|10 days ago
Warrior
avanderveldenWarrior

Search and open documents always visible on top of menuPlanned

Can the search and open document always be visible on top, also when you are scrolling down.In Windows GUI, the search is at least always visible, in Universal GUI all disappears when scrolling down in the menu  

7
Arie V
Forum|Forum|10 days ago
Captain
PeterKeerisCaptain

Make it possible to pin down Search and Open documents in the menuMerged

Most core applications have quite an extensive menu, easily creating a scrollbar for the menu, specially on smaller screens. When scrolling down, you lose sight of the Search field and Open documents which is quite annoying.Therefor I suggest to make it possible for a user to pin down the Search field, the Open documents and the Favorites (each with their own setting) so that they stay locked on the screen and don’t disappear when you scroll down in the menu. This settings should be saved as a user preference.I’d say the search field could be pinned down by default.

7
Arie V
Forum|Forum|10 days ago
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.

4
Forum|Forum|11 days ago
Harm Horstman
Superhero
Harm HorstmanSuperhero

Store SAS token expiration date in Application / File Storage SettingsNew

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 

0
Harm Horstman
Superhero
Forum|Forum|11 days ago
Xavier de Bondt
Sidekick
Xavier de Bondt

Native OpenTelemetry support for IndiciumNew

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. 

0
Xavier de Bondt
Sidekick
Forum|Forum|12 days ago
Robin Liu
Sidekick
Robin LiuSidekick

How would you approach a "tagging" system within the Universal UI?New

I think everyone here is familiar with tagging systems. The community posts themselves have the feature to add tags.I would love to implement something similar in our Thinkwise application, but am still thinking about what the best UX approach would be.The data structure you would work with is a linking table. However, showing the linking table as a detail tab of the main subject would not provide the smoothest user experience.Here are a few points that I think would have a large effect on UX but might need some “out of the box” solutions within the Thinkwise UI.It would be best if there were a control in the Form that works like the Column Filter. For read-only purposes an expression field works, but for editing this does not exist. It would be great if users can add tags that do not exist yet on the fly. Normally, they would first need to open a pop up of the Tag table and create a new row there, then select it. It would be great if adding tags was part of the same process as creating the main entity, because otherwise it’s so easy to be lazy and just not do the subsequent step of adding tags.The blog post about using Wizards definitely has given me some ideas, but I also know it can be nice to stick to the Form because people are used to it, so it’s more consistent, and it’s nice to have all fields visible. 

0
Robin Liu
Sidekick
Forum|Forum|12 days ago
Moderator
Erwin Ekkel

better layout for universal errorsNew

Please improve the layout of universal errors. This is the error starting with the query.  Then I have to scroll down half way to even find the error.  Please put the error on top to greatly improve debugging time.  

0
Moderator
Forum|Forum|12 days ago
Sidekick
peter.bongersSidekick

Create task or function to do smoke test of one table under dataNew

Smoke tests are running very long in a model ± > 300 tables. if you want to run for test. If it’s possible to execute the same tests for a selection of tables/views its easier to check changes to primary key of one table for example. Check mandetory fields in views as well.  

2
Sidekick
Forum|Forum|12 days ago
Warrior
avanderveldenWarrior

Change to TCP - supportCompleted

It would be very helpful ifyou can always add info to a ticket, also when it is processing (e.g. when you want to add some info / inform to close ticket). Now you don't have this option (buttons are disabled) to assess a solution, there is only an option to add comment in case you don't accept. But when you accept, it might be useful to add info (got give extra feedback to TW)

4
Arie V
Forum|Forum|13 days ago
Vanguard
MatteoSangiorgiVanguard

LLM Instruction - upload file (PDF) and ask a questionOpen

ChatGPT (open AI) now supports a feature where it’s possible to upload a file (PDF) and ask a question regarding that document.I see no connectors on TSF that can use this feature. This feature might be helpful to analyze documents (example: technichal documentation) and summarize it.

2
Captain
Forum|Forum|13 days ago
Captain
PeterKeerisCaptain

Handler for copy actionNew

I would like to be able to set a handler specific for a copy action that also uses the source row primary key as parameter(s). This way we do not need to create a specific copy task every time we want to include weak-entities in the copy action but the handler can execute that logic.This also has the advantage that the copy action is always at the same position in the action bar.

0
Captain
Forum|Forum|13 days ago
Raymond Gerritsen
Thinkwiser
Raymond GerritsenThinkwiser

Showing columns moved to _query suffixed tables as a detail of their parent table in the SFNext release

Query fields were moved to _query-suffixed tables in the 2026.2 version of SF. As a result model-info is no longer (correctly) usable on any query field. This is inconvenient when you want to develop dynamic functionality or query metadata at a higher level. I happen to be aware of this change from the latest SF release because I was involved with upgrading to the 2026.2, but a developer who was not involved in the upgrade would have a very difficult time figuring out where the query columns are actually stored. It would require a significant amount of investigation and trial-and-error to uncover the correct locations.My suggestion would be to add the _query-suffixed tables as a detail in the form of their parents to alleviate this issue.

4
Mark Jongeling
Forum|Forum|13 days ago
Harm Horstman
Superhero
Harm HorstmanSuperhero

HTML Tooltips in TreeviewOpen

I would like to request the addition of several core capabilities that are currently missing in the Tree View component:Drag & Drop  Add Expand All and Collapse All to (Custom-) Actionbar HTML Tooltip Lazy loading of child nodes to improve performance when working with large hierarchies

7
Harm Horstman
Superhero
Forum|Forum|13 days ago

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
Terms & ConditionsAccessibility statement