Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
It would be nice if the login page of the webgui uses the language of the browser settings, instead of using the INI. In any case for Dutch, German, Spanish, English and French.This would be a solution for applications with users from multiple countries.
Hi, I believe it is not possible yet to use the auto-resizing for column widths per column yet. You can only enable it for the entire view. However I would like to apply it to a single column of the view. It is something small but it would help to make some of the views clearer and easier to read
I noticed a lot of new user configuration options in the new interface.I think that it would be good to have a menu option with which you can reset one subject or everything in the application to default.
It's great that the user is able to configure the subject, but unfortunately the user has no option to return to the default configuration. Sometimes we have to reset values in IAM. It would help if the user could just restore the default configuration in the user preference.
I wish it were possible to define a base layer to visualize a secondary dataset.In our case show we have a data layer linked to work orders, while as base layer I want to show all possible worklocations within a construction project as base layer (static layer)
When I make an cube I would like to see the lookup values for related tables in the row and column headers.So that a row is not for customer_id 2387641 but for Jansen Enterprise BV.To accomplish that I now have to create a view that joins the customer table to get the name, use that as a base for my editable cube, and put instead_of triggers on my view to facilitate the edits. This is not really in the spirit of low-code.Can we please get lookup values in the row and column headers of a cube in the Windows GUI and/or in a future Universal implementation?
Hi Thinkwise,As most of our pages in our project have been moving to less forms, and for future ideas as we develop with the help of edit in grid and auto save features enabled. We were proposing for an idea for keyboard shortcuts for grids to be implemented the same way we implement them in forms. With this if I type control + shift + plus, in my keyboard add mode will happen. I know currently we can do this only in the windows gui, web gui (if I remember correctly), and universal gui for forms only.Enabling this will be a huge help for our users as they will be working faster within pages with grids only in combination with auto edit and auto save.Grid only pageThis is what CTRL + Shift + ‘+’ can do for now
Can you also make the double click function work for grids that are in (auto) edit mode?At least for 'Read Only' fields and when double clicking on the row selector at the left side of each column.It would also be very useful to be able to define a double-click task per column in the grid, whereby the tab_col_from_id is passed to the default procedure of the task.In many cases it is also desirable to be able to disable the zoom action for grids. Average users do not understand what is happening. It would be better if the zoom action was included in the context menu, for those very few times when advanced users make use of it.
We have a 2dline chart (see below) that shows values in time. The chart shows a subset of the values in the pivot table (around 1000 rows?). Is this a known limit? Is there a way to scroll in time?
For dynamic model with strategy ‘Staged’ it is important that everything that is connected, is in the same control procedure code field so that if something is removed from the model by the dynamic code, it is cleaned up without any errors. The result is dynamic model with many lines of code in one field that does multiple things. An example is the meta_view_history from the Thinkstore (Logging data available in the GUI), there is code for creating views, creating view columns, detail tabs, conditional layout and setting up roles all in one field. I think it would be an improvement if dynamic code control procedures could be separated into multiple code fields to be able to structure the code. This would make it a lot easier for maintenance. A possible way for doing this could be by adding the template level for dynamic model control procedures.
Per request of @Vincent Doppenberg & Rene JochemCurrently we have the issue that when we deploy an application for a new customer, the default start times of a systemflow are applied. When having enough applications on a server, the server gets busy with handling spikes of load. Now normally when having only a few applications and only a few customers this would be of no concern. But having a more than a few it becomes difficult to manage.We would like to see some form of randomization within certain thresholds we can set to let indicium (or some other service or mechanism) decide what would be the best spreading of starting systemflows to overcome these spikes and let it balance the load better. rgds Ricky
Hello TW,May I request for an implementation of “Pagination” in the “Resource Scheduler”.In our case we have thousands of records that we want to display in our “Resource Scheduler” that the screen component cuts the record with unidentifiable max no records.Resource Scheduler with “Pagination” sample. There will be cases where Scheduler will have multiple ‘schedule’ bars depending on how it is used, and it would be beneficial us if we can navigate to the records that we won't be able to see in the front page.
For barcode scanners it is unwanted that the on-screen keyboards popups once the barcode field gets the focus. This is possible by making the barcode field a combo lookup field so that the DisableKeyboardForAutoCompleteCombo setting will disable the on-screen keyboard. This has the negative side effect that the Universal GUI will load/show all possible barcodes in the combo field once the field gets focus. The Universal GUI needs quite some time for this when there are thousands of possible values in the combobox which creates a serious performance issue. It doesn't seem possible to limit the amount of values that are shown (it doesn’t respond to the ‘max no of records’ setting in the source table). Therefor we would like a different option to disable the on-screen keyboard for certain fields without needing it to be a combo field. For example when the field is using a domain with the ‘Barcode scanner’ control.
I would like to have a task to copy all settings and configuration of my table variant to my main subject.In running projects we often encounter screens that have grown over the years and have lost their efficiency. These screens need a significant overhaul in screen layout and available functionality. To overhaul a screen we often create a Variant in which we start moving things around together with the key users to create a more functional screen. This usually takes 1 or more sprints to finish.When the key users agree with the new screen layout. The variant should become the standard screen and should be brought live. This makes the current default subject configuration obsolete, and can be replaced.However it is not easy to copy all table variant information to the main subject. For this, I would like a task that copies all my table variant settings to my main subject. Just like the how the “copy table variant” task now does for creating a new variant.
Tracing back issues can be a pain in certain places. We all know that, especially when it is not code you’ve written yourselves and it was executed on machines you have to get approval of to get access for more information about whatever you need to examine this further.Indicium is mostly the middle man that may just about to knowing every single thing in the constellation of the application.Currently the errors in the indicium log barely give information about the context, where it was triggered, what has caused it to happen etc. For example which http request was it that triggered the error and which function/stored procedure/trigger/systemflow/what the actualy faulty SQL statement was etc… Sure you can gather every single logfile from alle the included servers in the whole process, including client action and try to match them all together, but a single indicium log entry that provides such crucial backtrace information is sooo much more convenient - I’m pretty sure you are not only making the debuggers and coders happy, but the whole nine yards from customer to servicedesk to systemengineers and sales and everyone in between.
For specific branches will be useful an option to set if a branch should/should not be editable.This will be useful for main/release branches (or others). You can view what is done, but not edit it, for that you can create a branch to fix a problem if is the case.It can happen by accident or not for someone to edit something in those branches, with a configuration like that, this will not be possible anymore.
Can we have such a toggle switch as a domain control? Using the main or accent color from the theme settings. For Universal this could be a powerful feature. In our case we want to define in the form if a customer needs to follow a certain extra process or not. This is a different application as a regular checkbox, which we also already have in the form.
For each field in your datamodel you have to set the data sensitivity. Often the same anonymization type is set for fields with the same domain. For example all email fields will have to use the sample set emails and fields using the domain remark will always have to be set to random value.It would save a lot of time and prevents data leaks if you could set up the data sensitivity anonymization type on domain level.
Having the System Versioned tables is very useful but in many cases it is not required to keep the entire history, often it is enough to keep the historic records of a certain time range. Always keeping the full history is a waste of resources. It would be a good addition to be able to set the required retention time in the model, this would save building custom after upgrade scripts to set the retention time after the fact.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.