Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Improve quality of merge results by making it easier to track which merge impact item has been checked. I check merge impact before effectuating a merge session. Most natural would be to do that by functional segment, but I tend to do it by type of object: I sort the merge impact by type of object, and then check all records of type kind of object and then turn that type off in the filter. After iterating over all types of object, all impact has been checked. The filter is transient though, so when there’s reason to reset the filter, I lose track. It would be handy to have a tick box available that I can tick after checking a record of impact.
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
For user notifications, please make it possible to send an in-app notification that is displayed as a popup message instead of a panel message. Panel messages are easily missed by the user, so by using a popup message the user actively has to close the message window.
When opening a menu item multiple times, they all get listed in "Open documents". It would be helpful to see which one you have currently open, especially when having multiple tabs with the same name.Can the active tab be highlighted? For example here, indicate which of the three tabs is the active tab,and maybe even make it possible to choose a display column to show behind the subject name.
Our user finds the scrollbar too thin to easily drag with the cursor, especially when doing horizontal scrolling.Of course there are options like using the scroll wheel, but many users aren’t accustomed to horizontal scrolling shortcuts.For people with disabilities it can be especially difficult to get the cursor on narrow spots.The compact/comfortable option currently does not affect scrollbar size.It seems that in browser settings it is not possible to adjust scrollbar size.We could apply custom CSS but (application wide) custom CSS is not preferred.
Within the code-review screens there is no way to see what code group the template you’re reviewing belongs to. If you don’t name your procedures something like def_do_this or ctx_do_that then there is no way of knowing what code group the template belongs to. Easy fix is to show that field in the code-review screen.
I read that Indicium currently doesn’t seem to support $batch: https://docs.thinkwisesoftware.com/docs/indicium/api#supported-odata-operations I think batch processing might be useful and efficient: https://www.odata.org/documentation/odata-version-3-0/batch-processing/
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
When a column is set to hidden and this column is not a PK, the column is often not supplied through Indicium. This is fine for most cases. However sometimes there are columns that should be hidden inside an application but should be available through Indicium. For example, an Interface ID column.Currently the only way to make this column available in Indicium is by setting the column to editable or read only and set it to hidden on grid, form and cardlist.I would like the option to enable a checkbox on role level that will make a hidden column authorized. This should result in the column being supplied through Indicium for this specific role.This way these kinds of columns can be made available to interfaces and remain hidden inside our application.
Currently as a user you can change several settings related to how you would like to use an application. Which setting you can set, is configured through IAM.I am missing 1 important setting in this. A setting to change the Timezone I’m using. Since all other settings related to your location (date format, language, number format) can be changed through this window, I would expect that the Timezone can also be changed from within this window.
Hello!I created this idea as result of this post: Basically, what we suggest is that there should be an option to specify the lookup control for grid filters, we received feedback from users about this and since that can be changed for form/tasks, will be nice to have it also in here.Regarding performance mentioned in the post, one solution can be to have the sort defined and then pick top 100 for example and if you don't have what you want there to still be able to type and search it.
When moving components around of a screen type it now is saved immediately. Please change it how it was in the older versions where an active “Save” was required to confirm your changes.When you now move a component and the result if the placement has an unintended result, your screen type is now ruined. Since the order of how you move component can be quite important to not completely mess up the already setup specification in width/height, a mistake can happen quite easily.
Often there are situations where you want to show a different tab-variant as a detail tab based on a specific property of the selected row in the main grid. This is possible by making multiple references and let the context procedure only show the detail tab with the tab-variant based on the property value.When there are multiple detail tabs for the main subject, this has one major downside though: Normally the GUI remembers the activated detail tab when the user switches rows in the main grid. However when the context procedure switches the reference for a different tab-variant, it activates the first visible detail tab.This creates inconsequent behaviour for the user when switching rows in the main grid because sometimes it does keep the same detail tab activated and sometimes it doesn’t. From the user perspective, the different references to the same detail tab are the same thing.To improve the behaviour of cases when the activated detail tab becomes hidden by a context procedure, the GUI/Indicium should prefer activating the first visible detail tab of the same target table as the previous activated detail tab (before activating the first visible detail tab).An alternative (instead of checking if it is the same target table) could be that it activates the first visible detail tab with the same translation value.
In Release notes Thinkwise Platform 2026.1.11 | Thinkwise Community aggregations for groups were added. Unfortunately there is only an extended property to disable this for all subjects.Please make it possible to disable aggregations for groups on specific subjects.
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.
I might as well have used the title "Semi-colons separated attachments for Email-connector (Storage attachments path)”, as the problem exists for both cases.I've been directed the a similar idea for Disk files attachements. Initially placed in the community as a question, but now I made an idea for it. Probably this idea will be merged to the Disk files idea.We want to get rid of local file storage and completely move to cloud storage ( for uploads amongst others). So the idea of having to move one or more, sometimes quite large files, to a separate folder, ZIP it en then send the ZIP file as an attachment doesn't really appeal to us (and is not very professional, as the customer has to figure out what is what in the ZIP file). See also Semi-colons separated attachments for email-connector (Disk files) | Thinkwise Community and **SMTP connector: sending multiple attachments from an S3 file storage location?** | Thinkwise Community
Have the preview component also abide by the theme colour it is set to.When there is no document/image to be shown or the size of it is way smaller than the component, it would be nice that the none relevant part of the component is actually similar to the theming colour.Working in dark mode and getting flash banged by the preview component is not fun.
On a Task or Report you can set the “Await result” value to “Optional”, so a user can move the process to the background when he/she does not want to wait for the result. In the older GUI’s you had them available in the “Running tasks” window and could see then progress on them. Running tasks windows (Win GUI)Unfortunately this feature is missing from the Universal GUI. When you have put several processes to the background, you have no clear idea what is still running and what has already completed or maybe even failed. A notification is not a valid solution to this problem, so this idea is for the return of such a feature.I am all for it to being a configurable entity, so you can also decide not to support this window in your application.Maybe it should even support the “Await result” value “No” to appear here, but perhaps we could also have other users give their opinion about this statement.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.