Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When you open the Universal GUI for the first time, or after an update I assume the full model is loaded, this can take up to a few seconds where you are staring at a white screen with not visual indication that there is actually something happening. This is quite unwanted, especially in situations where connections are slower. I would like to see a visual indication (like windows) showing that something is happening.
Within the functionality you can add a piece of code before, during and after a upgrade script, this is really usefull with data converisons, really like the functionality.But what I am missing is when I add a new function and need this function in the data conversion there is no place I can do this except for the manual script. But the manual script I have to delete after upgrading, otherwise this will be executing every upgrade.It would be usefull for me if we are able to make a upgrade script functionality but the really in the end which we can assign to a certain upgrade version x → version x.y
When you have a table/view variant where all prefilters are off and hidden for a prefilter group that is mandatory the GUI won’t fetch any data for that table and will never be able to for that variant. It can be quite the search finding out the cause of the problem. Since the combination of mandatory prefilter group with all prefilters off and hidden is something that in no situation is benificial and only leads to strange GUI behaviour I'd opt for an extra validation rule that detects this misconfiguration in the SF. I would have found the cause of the issue a lot sooner if there was a validation for this issue.
At this moment you can create different “data models”.I would like to be able to filter on those “data models” everywhere, and that the filter would apply for all the screens where it is appropriate.At this moment a lot of time is going to finding items in lists. I think it would be great if items could be tagged by the places where they are used. The data models could easily be used as tags. They are already there.So, an option to filter on “used in datamodel”, would limit the number of subjects you see.
At this moment it is not possible to activate a control in a input field in the Universal gui without using the mouse. In the Windows gui a control becomes active when using the tab. In Universal tab goes directly to the next field. Make a keybord activation possible to make using the mouse optional.
Most of the time a cube holds empty lines and empty dates as there is no data for the specific cube data cell.It would be a great functionality if could suppress these empty rows and/or columns if all empty.The red sections would then be suppressed if both empty rows & columns needs to be suppressed:
When using separate mock data sets for tables it is not possible to give a generation order number to the data sets. As of this moment the order of the generation of the mock data is in alphabetical order of the data set. Being able to give a generation order number to mock data will prevent error messages. An example of this can be found in the attachment
Hello!It would be nice and functional to be able to hide pre-filters based on the Layout-mode. In our case it is wanted to switch the pre-filters to hidden when ‘@layout_mode = Form’ and have the pre-filters visible when ‘@layout_mode = Grid’.Because when form is active it is possible to lose the current field when (accidentally) changing the pre-filters. Next to the functional part it also looks cleaner.I know it is possible in the Windows GUI to completely hide the pre-filters in Screen types but this option does not work in the Universal GUI and I would like to see to have the pre-filters visible in the Grid but not in the Form.
Make it possible to have in the preview of the document a set number of rows shown. For example: If I have an excel of 100 rows I want to be able to select the number of rows I want to be displayed in the preview.
I would like to suggest an alternative approach to using expression fields.I do realise that the best idea is to try and avoid using expression fields, but still they are often very useful and, but I see that they are handled pretty poorly, performance wise.The simplest example is that I may have 2 tables in which I would like to display more than one field in one table that belongs to the other table.Now the resulting query often is something like: select t1.field1, t1.field2, (select t2.fieldX from table2 t2 where t2.key = t1.key), (select t2.fieldY from table2 t2 where t2.key = t1.key) from table1 t1I would guess that the best way to go about this is to have a query that says something like: select t1.field1, t1.field2, t2.fieldX, t2.fieldY from table1 t1 left join table2 t2 on t2.key = t1.keyCould it be possible to facilitate this by, for example, creating joins on tables much like you draw references for check integrity, look-up or show detail purposes? When a reference like this is drawn between two tables they will join and you can draw information out of them by using their aliases instead of writing a complete subquery for each column you would like to show.
In the SF there is a tab "Subroutine options” since version 2018.3 (see Execute as option | Thinkwise Community (thinkwisesoftware.com),We now use this in a particular subroutine en during the creation proces this is “translated” to a option in the resulting procedure. I would like to see the same possibility with TASKS. Tasks in the end will also result in a procedure, just like a subroutine.I don't really understand how Thinkwise translates “EXECUTE_AS” to “ with execute as ...” but that asiide.And not just this. I would like to see more of this… For example, in a few tasks we want / need a “with recompile” option to have an acceptable performance. There are probably better ways to get a task running faster besides using “with recompile”, but for now this works for us.In Transact-SQL there are currently 3 options, I think, when creating a procedure, so it would be nice if all three are selectable per procedure (task, subroutine, default, layout…. actually everywhere that results in a procedure in the generation process).See also CREATE PROCEDURE (Transact-SQL) - SQL Server | Microsoft Learn
We need to switch detail tabs on or off, depending on the platform that is used. This because some screen controls are not available for all platforms, like the Card List.Creating different variants for different platforms is not a good alternative, because this results in to much maintenance and side effects.Having the platform_id available in the context procedure would be a perfect solution for now.Or, a global function, like dbo.tsf_platform_id() is also fine.
In our application we have a attribute table in which attributes can have different types. At this moment there is a context procedure to switch between fields to display. That makes that the application is not going to work offline.If it would be possible to say “hide in the form / out of form” in the conditional layout this would not require a context procedure and could also work in offline mode. There are a lot of scenarios in which control procedures and logic would not be needed, while they are needed at this moment. ( The conditional layout is already there so this is just a small addition ).I do have another idea, to solve the same issue which I will post as a distinct idea. I note “software factory” below as it should of course work the same in all GUI’s.
I’m trying to solve two things,In our application we have a attribute table in which attributes can have different types. At this moment there is a context procedure to switch between fields to display. That makes that the application is not going to work offline. Next to this we have a control procedure to hide tabs where users don’t have data to enter. For the first I added another idea but we could also solve this with this addition.Outline;I created a subject with a reference to a view. The UI understood that there was no record to show and that it wasn’t possible to add a record. Still, the UI showed the tab with an empty record. If it would be possible to choose to hide tabs with no data it is possible to do a lot of things without control procedures.Both “1” and “2” could be solved this way. For “1” this might not be the most efficient way but in case of “2” we could just delete a control procedure. With that data entry would “probably” work offline.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.