Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When pasting a value in a combo box, it selects the first value that partly matches the text. This is very annoying when you pasted the exact value that you want to enter. It forces you to manually scroll to the right record and select it or use the lookup window.If there is an exact match, it should prefer that over the first matching value.For example:
I use dark mode in the Software Factory and SSMS. It’s great that since the Software Factory is available via the Univeral GUI, that it supports dark mode.However, the Debug Center is missing this feaute and is always in ‘light’ mode:It would be great if the Debug Center gets dark mode as well since it’s used a lot during development.Yours sincerely,My eyes
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.
I would like to see the Model Insights window to be variable in size. We use very long names and can only see the first part of it.For example:
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.
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
When a finished branch gets merged to it's origin (non-reciprocal). It becomes finalized and, depending on selection, archived. Further merging into and from this branch is thereafter no longer possible. Yet, active development is still possible in a finalized branch (even after unarchiving). Wouldn't it make sense to completely lock development in a finalized branch as well? I have experienced a scenario where an unsuspecting developer was actively developing in a finalized branch (without knowing it was a finalized branch) and then find out way too late all of his work is for naught.
When deleting a row in the Software Factory, it currently shows the generic message:Usually you can see the selected row in the background, however, I’d like bit more assurance when deleting things in the Software Factory. It would be great if it showed for example (when deleting):Functionality: Are you sure you want to delete {control_proc_id} Branch: Are you sure you want to delete {branch_id} etc.
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
Hi Thinkwise community, We want to use the data type Hierarchyid. Hierarchyid is very useful for multi-level structures and is better for our performance. Now we use recursive methods but the bigger they get the slower they become and every time something changes you have to recalculate the entire tree.Unfortunately, this is not possible because the GUI does not support Hierarchyid. I saw a topic with a great solution by Anne Buit. Is it possible that Thinkwise can implemented this mapping? Thanks! Solution:“The hierarchyid is a type that does not have a direct mapping to any internal datatypes used by the technology of the GUI so a conversion must be made to a mappable type whenever this value is loaded into the memory of the GUi (e.g. to nvarchar(4000) and back to hierarchyid).” Topic:Support for System Data type - Hierarchyid
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.
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.
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.