Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
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.
It would be nice to have a option in iam to set an inactive timeout (in minutes). If a user is inactive for x amount of time that the session will be expired and the user will be logged out.
Instead of having to create multiple layouts, we want to be able to control the background color and font settings using expressions or a selectable columns in the table.Our current solution is ok, but it is laborious for us as developers and limits freedom for end users. I don't know, but I can imagine that it also has consequences for the performance of the application if a topic has so many layout rules? How we do it now…
IntroductionUsing the Universal GUI in multiple browser tabs can be really powerful. For example to make use of multiple monitors or not to clog the 'Open documents' when you want to open multiple rows of the same subject. When using a html field that points to a deeplink proces flow, it is already possible to make a clickable link in the grid to open a subject row in a new window. This is beneficial over double-click tasks because it works with a single click and it shows as a hyperlink making it intuitive for the user. However there are a few things that could be improved.Suggestions1. Make the title of the website page dynamically and configurable per subject. For example as default I want to use 'subject_name lookup_field' (Product P65434), but for subjects that have a recognisable name I just want to use 'lookup_field' (PO-32423). This would also be very useful for floating-documents.Optional:-Make it possible to include the application name.-Make it possible to use the tab icon as page icon.-Use a similar configuration to show the title in 'Open documents' (Open document title in combination with lookup | Thinkwise Community (thinkwisesoftware.com)). 2. Make it possible to use html fields as a lookup field for foreign keys. Currently it doesn't work when the lookup field of a table is a html field (even when the reference field in the target table also is a html field). The only way around this seems by using an extra html expression field in the list and the just the actual lookup field in the form (but this limits the use of add/edit in grid). 3. For proces flow action ‘Open document’, add an extra option to open as a new browser tab page.4. Make it easier to setup html links (this could probably be done already with dynamic code): Add a checkbox to a table column to enable ‘link to page’. When this is enabled for one or more columns in a table (or variant), in the background a process flow should be created to open the document (form) as a deeplink. Another effect of this checkbox should be that the enabled column should be displayed as a html link that points to the process flow deeplink on the same server/application.An alternative (in combination with suggestion 3) could be to add a single-click option to tasks. This should underline the single-click-field and show it as a hyperlink so the mouse cursor is changed making it more intuitive for a user). Screenshot Example expression field lookup that links to the source table in a new browser tab.
When the document has a lot of data with coordinates to be shown on the map, the application performance is very slow. Like in Google maps, it would be nice to filter all data based on a maximum and minimum latitude & longitude and the zoom level. So the imput of this functionality would be like: Center coordinate: 52.0907, 5.1214Zoom level: 10 (should be mapped to a distance in meters) And the output would be like : min_lat …max_lat …min_lon …max_lon… The output coordinates can be calculated using the reversed Haversine formula. With this data, the dataset can be filtered and the data & map wil only show the locations within the current position of the map.
Following session variables (similar to tsf_appl_lang_id) will help to make good performing queries that contain UTC to Local time conversiontsf_appl_time_zonereturns the end user time zone as is saved in IAMtsf_appl_time_zone_sqlreturns the end user time zone as is saved in IAM, converted to the time zone id in SQL Servertsf_appl_utc_offsetreturns the offset in minutes, between UTC and time zone that is set by the end user See also here:
In IAM and TSF a lot of duplicate actions and tasks exists which can be eliminated to make things much more clear. Keep just one of each that works or merge functionality into one task with options
We see a number of points for improvement for the login process.1. Make the login screen clearer for end users 2. Simplify the logout processIf possible, only 1 step without options 3. Simplify the OpenID provider screen in IAM by omitting unnecessary fields, offer default providers (Microsoft, Google, Facebook) in a lookup or task. More default values, hints, tooltips. Wider fields etc... As has been discussed with a number of people recently.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.