Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
A strike through is a perfect way to show users that something has been deleted, or is discarded for another reason.
Currently it is not possible to change a unit test it’s linked object. I would very much like a feature that allows me to change the object of a unit test. I can image that you are not allowed to change the object type.When do you need such a feature. For example if you split up a table into 2 tables. Or when you create a view of a table and you would like to also include unit tests from this table to be copied to this his new view.Or when you have to copy/split up a task. You would like to copy units or move them to the newly create task(s).It can also be very usefully when you only find out during running the unit test that you have linked to the incorrect object.As to be expected the output and input columns/parameters can only be preserved when they exists in the new object.
Please add an extra setting for tasks in SF to make it possible to select one of the following button sets to make applications more intuitive for end users.1: Execute - Cancel (default)2: OK3: Save - Cancel4: Yes - No5: Yes - No - Cancel
For a businesscase we have to set the color of a chart column to a specific color, based on the total amount. For example, when the column value <= 20 it needs to be shown in red.I recently created a ticket for this on howto activate conditional formatting on charts, but it isn’t possible at the moment. I think this will be very usefull for other customers to.
I like the new feature to customize CSS in Universal ith a custom.css. Is it possible to create this feature for in Indicium style.css too?
It would be nice if you could filter on specific values from (combination of) the current tab and detail tabs. For example: which employees have more than 10 vacation days and work in the Customer Solutions department.
Hi all,I use the tab page option to create a division between two groups in a form. This way, a specific layout is possible. In platform upgrade 2025.1 the collapsible form is introduced, triggered by the tabpage option.However, there is no option to hide the clickable part of the collapsible form. I want the layout to be the same, without the blue bar.Tab pages create collapsible forms with a clickable part (light blue bar)It would be nice to have the option to keep the layout of tab pages in Universal and hide the clickable part.One way to implement this, is to create a checkbox in Subjects → Component → Form. When selected (by default) the clickable part is shown and the form can be collapsed. When the checkbox is empty, the clickable part is not shown, the form is not collapsible, but the layout is the same. An option to hide the collapsible form can be implemented in this section.Kind regards,Rick
Dear all,We have identified that the groupping of records for the scheduler can be configured only by 1 column and it is not possible to have more than 1 currently.The idea is to be able to specify the groupping level and have a Treeview as first column of the defined groups in the scheduler.Similar to what was in WEB GUI:
When double clicking on a row in a detail, you now will open a new main document with that detail. Sometimes it is useful when this new document becomes floating, so one can check some data on this document and the original document. To help the user minimise mouse clicking, we would like the document to be floating directly.I suggest to make this option configurable in the model, so the developer can configure on a subject how the zoom action will be performed.For now it is a hard way to model this:for each detail one would like to have this functionality is needed:a task containing the primary key of the subject, add it as a table task, with double click on record “on”a process flow, with the tab task as starting point. A process action opening the document required, and a process action to filter the new document to the requested primary keyAlso, the main screen type of the subject should be the zoom screen type, in order to get the result needed. One even might have to create a variant on the subject to use the right screen type.
Hi. In the Universal GUI when you say in the SF to put something in the next tab it creates a new section. To have the same experience as putting something in the the next tab.. it would be nice have a section collapsable, so by default it doesn't clutter the screen and you can just fold it open when you want to see these details. And perhaps it can come with an extra setting to have only one section open at the time or multiple.. just like with pre-filters where you can have only one or more.
Hello everyone,We have a process flow that pops up a window. This window is very small and should be larger when it pops up.We can set the default window size of all windows and pop ups in the software factory, but we do not want all windows and pop ups in the entire application to be the same size when we set it for the purpose of one window.Can this be set per window when you select the pop up option in a process flow for opening a document?When this option in this process action is set to "Yes” it would be nice to have an option to set the size of this floating document, so we do not have to set a general size for all windows and pop ups, because in come cases this can be unwanted.
Currently as a developer you are able to set the default column width for columns on a specific table. This will overrule the default column width set on project version level.This is a very useful setting, especially when developing for the Universal UI. Currently such a setting does not exist for the task and report parameters. Often when developing task and/or report popup windows one or more field contains a long text, for example the name of an item. Without being able to set specific column width for this task/report I am unable to increase the field size. Therefor I would like to set a setting for setting the column width on task/report level.
There seems to be a relationship between the grid height setting and the height of the grid header.I think this is not correct and the height of the header should only depend on the content of the header.Are the UI/UX developers aware of this illogical behavior? Can this be fixed?
As far as i can see, there is no option in the SF to define default values for subroutine parameters. When a default value could be defined they become an optional parameter in SQL server. I would like to suggest this add such an option in the SF?The advantage is that you don’t have to define all parameters when calling a subroutine.As far as I can see is that in the subroutine parameters an extra field should be added with default value. In the generate process the declaration of the parameters need to be changed so the variable will be declared as:create procedure proc_1 ( @a id @b id = 0) as begin In this case @b becomes an optional parameter and when calling procedure proc_1 there is no need to pass a value for parameter @b
Currently in the code deployment screen it is quite difficult to see whether or not you have already deployed your code. The icon used for this is very confusing. It is a green checkbox indicating you are finished. However, this only means to code is generated and ready for deployment.I need a better way to identify that the code generation is completed but the code is not deployed yet. This could be resolved by either changing the current icons or set up 2 different fields to indicate the status of the code generation and a second field to indicate the status of the deployment of the code
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.
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.