Recently active topics

As a developer, I want the “Database event log” readability to be improved.At the moment, the queries in those logs are not structured enough:Original topic text:On debugging I use the debug information/pane all the time and I’m pretty sure I’m not the only one.Really important information in this debug pane is the content of the form parameters and f.e. the task parameters. If these are lookups we can see the ID’s of the related tables there.As far as I can see now there is no way to view this info in the Universal GUI. That’s huge ommission when developing and it holds me back from developing in the Universal GUI. You’re working a kind in the blind… Hopefully I missed something in the documentation (However I’ve searching for about an hour) but this really important information should be visible as debug info in the Universal GUI. I’m a functional developer so I need values of the data being displayed and the underlying ID’s of related tables. In many cases issues in applications are

Could checkbox colors automatically adjust based on the background color (similar to how text already adapts for contrast)? This would improve readability and overall UI consistency  

I would like to be able to go to a row in the grid based on what I’m typing and the value of the selected column in the grid. (quick search?)The reason for this would be to save users the action of having to go to the search bar (which currently still requires the mouse, we would liek it to be keyboard only) and having to wait for the results to be retrieved again, even though the relevant data was already retrieved, it just wasn’t selected.This was a feature in the Windows GUI and it would be great to have this again in Universal, perhaps with some highlighting of the typed characters in the resultMy use case for this is order entry, when selecting order lines from a list of relevant products

When a column is set to hidden and this column is not a PK, the column is often not supplied through Indicium. This is fine for most cases. However sometimes there are columns that should be hidden inside an application but should be available through Indicium. For example, an Interface ID column.Currently the only way to make this column available in Indicium is by setting the column to editable or read only and set it to hidden on grid, form and cardlist.I would like the option to enable a checkbox on role level that will make a hidden column authorized. This should result in the column being supplied through Indicium for this specific role.This way these kinds of columns can be made available to interfaces and remain hidden inside our application.

In the Universal GUI we are missing tooltips in radio buttons options. It would be nice if we could translate options as abbreviations and see the translated tooltip when hovering over the option itself. In the print screen below you can see that Fresh produce uses its default translation as a tooltip (because it is too long). CU can not be shown as a tooltip yet. 

Just like with tasks, I would like to create and use dummy reports. The reason for this is so the icons in the application are better ordered. Tasks are with other tasks and reports with other reports.Left Tasks - Right ReportsThe reason we need a dummy report is to start a process flow. The process flow then activates a task that will insert a row in a sort of Queue table. This queue table will limit the selection of rows that DevExpress will use to make it's report; thus making the process a lot faster.So this task need to be run before opening the report. But the task cannot be the starting point for the process flow and therefor we need to use a dummy report.

Currently it is only possible to download one uploaded file at a time in the GUI's. A user asked to create a "Button" to download selected documents (one or more lines with one or more fields with a FILE_UPLOAD control). I've been thinking how to do such a thing. My biggest problem is that a function that I could write has no access to the location where the actual uploaded documents reside. But how cool would it be if the GUI "detects" file_upload control fields in a list (or form) and shows something like below to download all documents at once as a ZIP file?

The thinkwise platform is very powerful as it comes to referencing information and one of the results is that the screen gets bloated with tabs up till the point there are just too much. The fact that you can have horizontal and vertical tabs is already great.  However I would like to be able to group tabs to deal with larger tab-lists and references that functionally can be grouped for better understanding by the user.Like below, where there can be maybe a left-border color for the status references or just some white-space between the status-group (first-four reference) and the other ones. I guess a bit like the pre-filter, task and report groupings.   

When using the Universal GUI in Mac OS Safari, the fact that all edit fields use autocorrect by default, is very annoying. For example, when searching for a partial customer name, at one time you see the you typed enough characters to find the record you want. When you then navigate away from the search field, autocorrect kicks in, and often the autocorrected partial name is not what you want. Then the grid is empty or at least changed.As far as I see, this only happens in Safari, because Chrome does not have autocorrect.It seems disabling autocorrect is only possible / necessary in Safari and Firefox: https://caniuse.com/?search=autocorrect Being able to also disable autocorrect for form fields and grid fields could also be a handy feature. But there it could probably default to autocorrect=on for most text fields.

We often have situations (especially on status fields) were a user is only allowed to use certain element values or to move it from one element to one other element. The availability of a given element would be based on User permissions or current status (for example: if current status is A, you can only change it to B, and if current status is B you can only change to A or C, but not D). The current ways of resolving these situations feel like workarounds, which should not be necessary for such a straightforward request in a platform called low code. Suggested solutions I have heard are:Create two (or more) similar Domains with similar, but not all, Elements and determine in the Layout procedure which one to show. This basically means adding (sort of) duplicate domains, which is ugly and risky from a maintenance perspective... Use a Lookup to a Table or View with Pre-filters. This is more effort, clutters the Data Model and is probably worse in performance than a Domain with Elements.

Unfortunately, it is still not possible to subscribe to receive notifications for new arrivals, so good ideas can easily be missed and forgotten.I was thinking of a possible workaround, as long as GainSight can't provide a solution...Is it not possible to build a workaround within the capabilities of Thinkwise and have an overview of new ideas sent weekly from TCP to notify all users with a Thinkwise account?Download ideas with HTTP Connector, etc...https://community.thinkwisesoftware.com/ideas/topics?page=55&sort=%7B%22createdAt%22%7DSee also: 

Please chance the default screentype for screentypes in the SF. Currently assigning is a tab, which is very confusing. Please make assigning a detail instead. Current situation: Suggested change:  

Some mouse clicks less by simply combining Save and Select in one button in Lookup forms  

We would like to have the ability to show table tasks on a grid line. This is especially useful for the mobile GUI and when just a couple of table tasks are available. Currently you can show tasks on the top or bottom of a grid in mobile. To start a task for a specific record you should select a line first and then select the concerning task. In the described case it is faster to select the task direct on the line. See print screens for further explanation. Task on top of grid (current situation) Example tasks on grid line

When upgrading the platform to 2026.1, we waited for around two hours in total (SF and IAM on DEV) for the TSF optimizer to finish rebuilding the indexes. This was even after old branches/applications were removed in SF and IAM the day before to speed up the upgrade. At one point, we saw the slow_query_log index being rebuilt, where fragmentation was only 0.1%, containing over 5 million records. Our idea is twofold:Parameterize or hardcode the index optimization so that only indexes with a fragmentation percentage above a given threshold are rebuilt. Allow configuration in the Deployer to specify whether indexes need to be optimized. We already have a nightly job that performs this, so we would prefer to let that run outside office hours.