Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
The SF and data domains offer little possibilities to control the presentation of numbers. I thought the custom_display_format extenders would be the solution but I found some shortcomings that make them less useable in practice. I discussed this with Thinkwise people: The current behaviour is as intended but they think the following would be a good improvement.Simple example for a currency datatype NUMERIC(18,3) where users normally want to see only 2 decimals but the extra decimal is needed for calculation accuracy. By using an extender with "€ 0.00" format for the domain you get the following behaviourPositive:Display with 2 decimals is correct and third decimal is used for rounding up/down correctly An entered number with 3 decimals is correctly stored in the underlying tableNegative:When EDITING data there is no way to see the third stored decimal When EDITING it is not possible to edit the existing number; you have to clear the field and reenter the complete numberThe behaviour is the same in grid and form screens. We would expect behaviour like e.g. Excel:Display data using the Extender. They are called custom_display_format for a reason I think. Possibility to edit the exact stored dataWithout this behaviour the introduction of the extender seems of little use; the same could be achieved using an expressions field. But a task would be required to edit data and this is what we want to prevent.An extra improvement would be if the scope of the extender could be specified on a lower level than a domain. Then you would get the possibility to present and edit the same table field in multiple ways; the exact data for the finance department and in another screen rounded numbers for sales but still the possibility to edit the exact number.
It would be nice to have a variant_id for layout , context and default
We utilize variants extensively in our platform as this is one of the powerful benefits of Thinkwise. However we encounter pretty often that we want to build tasks and even layouts that should behave slightly different based on what variant they are opened/used from. Currently there is no real neat way of having that information available in the code/flow so we often have to resort to, in our opinion, janky solutions. If its possible to add the current variant as input parameter this would open many doors and possibilities.
I have a view with 3 fields that can be automatically filled (default proc) when selecting one value from a view having all three values concatenated.This makes finding things a lot easier for the user. The field is only defined in the view and nothing is stored in the database…. A similar situation now exists in a table. There is currently no need for a view instead of this table, so an expression field could be the solution here. Expression fields in the SF however are by definition read-only. So why not have the developer deside whether an expression field is read-only or not; most of us are wise enough to know what we're doing. To show what I mean, see link below… I made an expression field editable using SQL on the SF database, and you;ll see what I want to achieve. Works fine according to me. https://mcmurdock.stackstorage.com/s/4pGhtJXw03Y9EH8
Sometimes there are things that are linked to a variety of subjects, like relationship that are linked to objects or object_parts or contracts. Now I have a subject in which I want to use a relationship, but sometimes I would like to add a relationship that is linked to an object and sometimes I want to add a relationship that is linked to a contract. I thought I might use a variant that uses a lookup for relationship for objects in one instant and a lookup for relationships for contracts in the other instant. However the lookup of a variant cannot change and is always the same as was specified in the default. I would like to be able to assign a different lookup table to a variant.
Could you make an adjustment to the barcode control to enable committing with Enter, since the Tab key is not present on the on-screen keyboard of mobile devices?
I would like to be able to go to a row in the grid based on what I’m typing and the value of the selected column in the grid. (quick search?)The reason for this would be to save users the action of having to go to the search bar (which currently still requires the mouse, we would liek it to be keyboard only) and having to wait for the results to be retrieved again, even though the relevant data was already retrieved, it just wasn’t selected.This was a feature in the Windows GUI and it would be great to have this again in Universal, perhaps with some highlighting of the typed characters in the resultMy use case for this is order entry, when selecting order lines from a list of relevant products
Sharing functionality for TCP contactsToday I wanted to easily share a contact from the TCP application with a colleague, but there is currently no direct way to do so. In modern applications, the ability to quickly and securely share information is considered a standard feature.Therefore, I propose adding a user-friendly sharing option, for example via a deeplink. This would allow users to share relevant information with colleagues or other authorized users in just one click.Why this adds value:Improves efficiency and collaboration between users Aligns with expectations of modern software Saves time and eliminates the need for manual retyping or screenshots Can be implemented securely based on access rightsIn short: a relatively small enhancement with a significant impact on usability and productivity.
In the Universal GUI we are missing tooltips in radio buttons options. It would be nice if we could translate options as abbreviations and see the translated tooltip when hovering over the option itself. In the print screen below you can see that Fresh produce uses its default translation as a tooltip (because it is too long). CU can not be shown as a tooltip yet.
Some mouse clicks less by simply combining Save and Select in one button in Lookup forms
It would be great to have a way to automatically generate certain roles. For example, by using AI. Creating roles is quite a lot of work and something that often results in minor mistakes. Some how it feels kind of strange that there is no way to get some roles for free. Without having to do any work.I think that it can, and should be, possible to generate certain roles and therefor get these for free. Like get a read only and a management role for each menu entry.The read only role has access to the subject and all the visible details, but only ready only access.The management role has access to a subject and all the visible details. This role also has access to all the prefilters, tasks, reports and can insert, edit and delete on all these subjects.Having these roles available will save up quite some time. Since around 80% of your roles you will need is a management and read only role per menu entry.This might seem like a lot of work, but it could already be created through the enrichments. And with the coming of a MCP layer that should that simpler to implement.
We often get requests from our business to show a popup form when adding a new record instead of going to a form tab (or have an always shown form below a list). This is a behaviour that is present in many other systems. This is currently done by creating a tasks that shows the same fields as the form, a lot of duplicate, extra, work and lots of places for new bugs to be introduced (rights, defaults, layouts etc etc).Would be nice if we can just select the flow that happens when creating a new recordsCurrent behaviour (default) Show popup formMaybe even support this when doing edit etc.
As a developer, I want the “Database event log” readability to be improved.At the moment, the queries in those logs are not structured enough:Original topic text:On debugging I use the debug information/pane all the time and I’m pretty sure I’m not the only one.Really important information in this debug pane is the content of the form parameters and f.e. the task parameters. If these are lookups we can see the ID’s of the related tables there.As far as I can see now there is no way to view this info in the Universal GUI. That’s huge ommission when developing and it holds me back from developing in the Universal GUI. You’re working a kind in the blind… Hopefully I missed something in the documentation (However I’ve searching for about an hour) but this really important information should be visible as debug info in the Universal GUI. I’m a functional developer so I need values of the data being displayed and the underlying ID’s of related tables. In many cases issues in applications are data related!!!!
The thinkwise platform is very powerful as it comes to referencing information and one of the results is that the screen gets bloated with tabs up till the point there are just too much. The fact that you can have horizontal and vertical tabs is already great. However I would like to be able to group tabs to deal with larger tab-lists and references that functionally can be grouped for better understanding by the user.Like below, where there can be maybe a left-border color for the status references or just some white-space between the status-group (first-four reference) and the other ones. I guess a bit like the pre-filter, task and report groupings.
We often have situations (especially on status fields) were a user is only allowed to use certain element values or to move it from one element to one other element. The availability of a given element would be based on User permissions or current status (for example: if current status is A, you can only change it to B, and if current status is B you can only change to A or C, but not D). The current ways of resolving these situations feel like workarounds, which should not be necessary for such a straightforward request in a platform called low code. Suggested solutions I have heard are:Create two (or more) similar Domains with similar, but not all, Elements and determine in the Layout procedure which one to show. This basically means adding (sort of) duplicate domains, which is ugly and risky from a maintenance perspective... Use a Lookup to a Table or View with Pre-filters. This is more effort, clutters the Data Model and is probably worse in performance than a Domain with Elements...A possible solution that comes to mind is the ability to set in the Layout procedure when to show/hide certain Elements. It would be good enough if somehow the Layout procedure recognizes Domain with Element type of fields and we can write logic on each individual Element within that Domain. How do you like this idea? If you have other suggestions than the Layout procedure to fix this: let's hear it!
Unfortunately, it is still not possible to subscribe to receive notifications for new arrivals, so good ideas can easily be missed and forgotten.I was thinking of a possible workaround, as long as GainSight can't provide a solution...Is it not possible to build a workaround within the capabilities of Thinkwise and have an overview of new ideas sent weekly from TCP to notify all users with a Thinkwise account?Download ideas with HTTP Connector, etc...https://community.thinkwisesoftware.com/ideas/topics?page=55&sort=%7B%22createdAt%22%7DSee also:
We’ve used the Redgate SQL formatting (also mentioned here SQL-code formatting guidelines renewed | Thinkwise Community) in Azure Data Studio for a while. As of february 28 2026, Azure Data Studio is retired, so we’ve moved back to SSMS.Recently, Redgate has disabled the free use of this tool.It would be great to implement a similar feature into the Software Factory or the Workspace Listener.Redgate uses JSON to setup the preferred formatting style. Perhaps a similar system (either JSON or a table in the SF) can be implemented where the Thinkwise formatting guidelines are setup as default formatting.
There are currently 4 ways to open a menu item from the navigation sidebar. User opens a menu-item by CLICK or keyboard-select/ENTER. This opens the menu item in the current browser tab. This is correct behavior (no changes proposed). User opens a menu-item by ALT+CLICK or keyboard-select/ALT+ENTER. This opens the menu item as a new browser window. The following improvements are suggested:The new browser window misses parts of the browser topbar (it shows URL bar only). Improvement: open as a regular browser window. The navigation sidebar is missing in the new browser window. Improvement: open the browser window with the navigation sidebar visible ALT is not the universal browser convention to open links in a new browser window. Change this to SHIFT. User opens a menu-item by CTRL+ALT+CLICK or keyboard-select/CTRL+ALT+ENTER. This opens the menu item as a new browser tab. The following improvements are suggested:The navigation sidebar is missing in the new browser tab. Improvement: open the browser window with the navigation sidebar visible CTRL + ALT is not the universal browser convention to open links in a new browser tab. Change this to CTRL (also: scroll wheel click). User opens a menu-item by SHIFT+CLICK or keyboard-select/SHIFT+ENTER. This opens the menu item as a near-full screen focused pop-up. The following improvement is suggested:SHIFT should not be used for this as that is the universal browser convention to open links in a new browser window. Change this to CTRL +ALT (or another combination that does not interfere with standard browser conventions). Note 1: all above is described from a generic Windows desktop user perspective. Thinkwise to align this to Apple and Android OS’es as needed. Note 2: the browser context menu when right-clicking on a menu-item should also include default options such as ‘Open link in new tab’, ‘Open link in new window’, etc. It currently does not show that.
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!
A request I heard a lot from users over the years is to make it possible to select multiple rows in a lookup window and add them all at once. I don’t see a reason why it shouldn’t be possible if we accept the following limitations:The user must be adding a row (not editing). All fields (excepts for the lookup field) must be optional or filled with a default value. So no user interaction is required to add the row. Although maybe it could be possible to allow mandatory fields that are not filled with a default procedure if the user just enters it in the first row and the same value is used for all rows. So if the user wants to add multiple rows, he presses the ‘Add’ button, opens the lookup window and select multiple rows. The GUI should fill in the first row, save the row, automatically add the next row with the next selected value and continue this until all selected values are added. The default/layout procedure should be executed for each row. If one rows encounters a problem, for example one selected value is rejected in the default procedure, It should skip that row and continue with the next one. A same kind of summary popup with failed rows could be shown to the user as is done with the mass-update feature.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.