Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
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?
I wish to have the “On Change Prefilter” event available as starting point in process flows. Would that be possible?Based on the activated prefilter, other prefilters can than be automatically set on or off. By doing this, invalid filter combinations can be eliminated, that improves usability, and guides users toward valid selections only.We do of course make use of prefilter groups, but this is not always possible.
Currently, the cube view filter only supports “Contains” (or “equal to”) as a filter option.Additionally, I would like to have the option for "does not contain” (or "not equal to”) as a filter option.Now I have solved it with a prefilter that excludes my values from the cube, but it would be better if the filter option was editable from the SF
The option Apply to Tree is missing here:
Will it be possible in the future to apply Infinite Scrolling to certain Card Lists, Form Lists and Grids in our applications? We would like to see it as an extra option in subjects.For some screens it is desirable to have this, especially for small mobile devices, this can gain some extra available height, and avoid scenarios like below:Is this technically feasible or are there good reasons not to want this?Or is this something that can now be achieved in the Univeral GUI, using custom CSS?
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.
I came across a story , and it mentioned a few AI cases that seemed interesting. Are there any movements towards adopting these type of technologies? There is a specific mention on 'question to SQL generation'. It would be great to have a user type in a question and the systems generates the right query to fetch the data and show it.
Currently, Thinkwise supports a Multiline control for plain text and an HTML control for formatted text. However, the HTML control requires HTML input, which is difficult to generate and maintain — especially in AI-driven workflows where markdown is the natural output format of language models.A native Markdown control would allow developers to store content as plain markdown text and render it as formatted output (headings, lists, bold/italic, code blocks) in the Universal GUI — read-only in grids and forms.Use cases:AI-generated content (user stories, descriptions, summaries) rendered directly in the application Documentation or knowledge base fields Any field where structured, readable text is needed without the complexity of HTMLProposed behavior:Read-only rendering of markdown in form and card list components In edit mode: plain text editor (like Multiline), or optionally a markdown editor with preview Available as a domain control, similar to how Multiline and HTML are currently offeredThe HTML control already proves there is demand for rich text rendering in Thinkwise applications. Markdown would be a lightweight, developer-friendly complement to it.
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.
In case only one tenant exists it would help to create default rows in these tables when a web domain is added: :web_domain_allowed_tenantweb_domain_login_optionElse nobody will be abble to open the application and there is no other way to solve the problem via the IAM database
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
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’.
Too really make the scheduler more useful, the tooltip should be HTML or at minimum have a more readable style + link for a deeplink for example.
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?
When nodes are filtered using the combi filter, the parent nodes of the matching results should always remain visible. Otherwise, the context of the filtered nodes is lost, making it hard to understand where the results belong within the tree structure.Example and desired behaviour:As an enhancement, we would like to see a model setting that allows developers to control this behavior. For example, an option such as "Show parent nodes when filtering" could be added to the Tree View configuration. When enabled, all parent nodes of matching results would automatically be displayed, preserving the hierarchical context while searching.
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.
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.
Could the Application log be enabled on the Software factory please?I think it would help finding out ‘how something got there’ when a developer created a strange situation. It could also help with tracing what AI did through MCP.And of course it could help with analysing performance issues. I would prefer it to be available SF-wide (over all models/branches), with the possibility to filter on a model/branch (prefilter for current branch).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.