Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
IdeaMy idea is to turn workarounds for hiding column translations into a formal option.ReasonFrom time to time, it happens that you don’t want to show a column translation.Consider an image combo that appears first in a grid:The current workaround is to enter a space in the grid translation field, as this is a required field for columns.Or a form where a label is not desirable because the context is already clear from the form group label:The workaround here is to set the label width to 0. Despite this, the translation is still being passed to the GUI in the background.
What I am really missing at the moment is a way to jump from my task (or subroutine or processflow) to a screen which contains all the related (assigned) control procedures and templates.We have the go to code overview screen. But this is not what I need when I want to make a change to my task/subroutine or processflow. Because I want to change to assigned code template(s). Having a button on the object called “Jump to code templates” which will open a screen contains all control procedures with assigned templates is what I need. It will only show control procedures and templates linked to my object. In the case of a task this is would be all linked defaults, layouts and tasks controle procedure + templates. In case of a processflow this would be all process control procedures linked to a processflow step.I should also be able to generate and deploy code from this screen.
At the moment I really miss the option to filter within my Tile menus. The Listbar and Tree menu types offer a filtering option, but the Tile menu does not.I often get the question from clients to enable filtering in the tile menu, but since this is not available have to tell them this is not supported.From a personal view I also would really like this feature. Because as an admin, I get to access to a lot of tiles and often lose sight of where I placed the tile which I have to open.
The way extended properties have to be configured is too complicated. First find the right Extended Property in the documentation etc...Why not show all extended properties and fill them with default values at first use and show all possible options per property with a lookup?
We need to be able to open a document from a process flow, not as a new screen, but as a pop up screen.
It would be great if in the Universal GUI the breadcrums are expanded with the information from the selected level below. As shown in the screenshots, this works now in the Windows GUI.
With the TSF 2025.1 version, it has become possible to expand/collapse form tab pages in Universal. However this is currently only configurable on the subject (default expanded or not). We would like to be able to influence this from the layout procedure as well so that tab pages can be collapsed based on the data and can even become dynamically.
Since process flows can be scheduled it would be valuable to have this feature available.Especially for environments that use AzureSQL, because they don't have an Agent to schedule jobs.Personally I prefer to use Procedures for scheduled jobs, instead of tasks. I only use tasks where in case only where user interaction is applicable.
When working with process or system flows, I often want execute a specific bit of code depending on a case. Currently I either have to use system tasks (which has all sorts of issues and limitations) or use the decision step and include my code or call of a procedure in this decision step.It would be great to be able to include the call of a subroutine as a process and system flow step. Also it should be possible to use this process step as a start of a system flow.This will prevent the incorrect usage of system tasks and include code, which should have been stored in procedure, in a process procedure.To summarize, be able to include a subroutine of the type procedure in a Flow, either system or process. Also be able to map the output values of the procedure into Flow parameters.
Especially with the introduction of the actionbar component, where you can freely position the actionbar it has become more a necessity to model the action groups of the actionbar. I see the taskbar has the following main groups:Filter Pre-filter Tasks Reports CRUD actions (incl. import/export) RefreshIt's not uncommon that you have a grid, form and for example a preview/cube/ or other element not being a reference.. If you put them all on a separate tab all the component gets all the action bar items. Functionally and personally this is unwanted. the filter, pre-filter and mass update for example do not make sense on a form level (exceptions are there of course) because you are looking at a single entity. In the U-GUI we use the previewer to load external apps.. Basically you don't want to have search, filter, CRUD actions there (again exceptions are possible)It would be really great if the option to hide action bar could be extended by modelling at screentype level which action-bar items you would like to see. Example: If you put a form on a separate tab, the search /filters are most likely unwanted because it will most like likely changes your context if you (accidentally) fill something in the searchbar or activate a pre-filter. If you have, like we external components that base themselves like a form on a single entity you have the same situation.. you probably only want to see tasks/reports and a refresh button here.. Especially when you are not familiar with the concept of Thinkwise it's odd to see have search / CRUD actions here. @tiago @Yara
Introducing a hover-to-enlarge photo feature in the grid can significantly enhance the user experience and improve data density. This functionality allows users to quickly and easily view larger versions of images without needing to click or navigate away from the current page. By enabling users to see detailed images on hover, it reduces the need for additional space to display larger photos, thereby optimizing the use of screen real estate.
In IAM Models and Branches kan be cleaned up by using the delete button. If you accidently had selected a model instead of a branch, the whole model is deleted including all branches.If all groups and roles are implemented in the SF a sync could fix the mistake. If not you're left with restoring the IAM database.Today I accidently removed a model instead of a branch this way. I now depend on IT to restore the database. Luckily it was no production IAM.My idea: present the user with a popup and having him/her selecting wether to delete a model with all branches or not. If it is up to me, deleting a model that has branches shouldn't be possible at all.
Elements grid in Domains is currently not editable, which is annoying, because domains can have many elements.
At the moment, the only way translations could be added for a table variant is by setting Translate flag on in the Settings tab page of the variant:Settings tab pageIt is easier and more intuitive to do that directly from the Translations tab page of the variant:Translations tab page
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.