Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
This idea came about due to having a column with a dropdown control (records selectable though a reference to another table/view), but wanting to always have the records on display and not just expand the dropwdown on click.Thus, the issue at hand is to always have the records visible on screen for that column.We would be interested in a solution that displays the records as separate selectable checkboxes (see image below). The checkboxes can be selected as a domain control type, but they do not produce this result. It is possible, however, that we might be missing something. The context behind this idea is a very specific one. We have made this with a view, however, for our purposes, it gets to have an inconsistent feel due to other functionalities in our table. Having them be displayed with checkboxes like above, instead of a dropdown, would be a perfect solution. We would also be open to a solution that could force the dropdown to always be expanded, thus removing the need for an extra click.
When Im running a creation script that fails I’d like to know the line number along the error message. This will give me a indication where the error is located.
As it is now double clicking on a detail tab in universal does something that, is as I see it confusing. One of the things is that I suddenly have another page, and that I don’t have an option to go back to where I was. Accidentally double clicking a tab results in being lost. There are also some bugs I noticed in the software factory; if you double click on a tab with an active search filter the zoom window doesn’t show the search filter but does apply it. Web and universal are different then a windows interface and I don’t think that this functionality will ever work the same in universal as it does in windows. I would like to have the option to create a workflow which opens an item after double clicking in a big almost screen size popup window with a close button in the upper right corner. ----This might already be possibleThis might already be possible with a workaround I did not try; create a screen type without detail tabs, create a detail tab, open the detail tab with a workflow starting with double click, add a big back action button in the upper right corner, add the back route to the workflow.The problem with this solution is that it will create a big spider web workflow, if you want all entities to generally be clickable and generally show a popup window, and you have for example 10 different entities which relate to each other, …, I don’t know if someone can think of a smarter way but I end up with 10 forward tasks with each 10 table tasks, 10 table variants for each entity and 10 backward tasks with table tasks for each entity, and a workflow which can be started by 100 different table tasks. ---The big challenge behind this idea is to make this possible with less “low code”. My first idea is that you could add a checkbox “Zoom on doubleclick” (in the SF) for all subjects / variants for each “zoom” detail. That way my example above reduces to one detail mapping in the forward relationships, but Universal has to remember the back route and show it in the interface.The result should be that it is possible to generalize opening popups with detail information.(It is also possible not to reuse the zoom screen type and add a popup screen type to all the entities, it is more work but might be cleaner).
With the help of breakpoints we are now able to design screens that work well on almost any screen size.However, some screens are specifically designed for the desktop and it makes no sense to have them available on smaller devices, such as those of a mobile phone or tablet.I wish there was a way to indicate this in the model. By means of a special breakpoint, or menu item setting, which ensures that menu items for these screens are only available for screen sizes within a certain range. Typical examples are schedulers or plan boards.
When importing a file using the standard import functionality it is possible to use default logic on the imported records (by using @import_mode). It is at this moment not possible to identify the importsession. Therefore it is not possible to distinguish currently imported records from previously imported records. I would like to see a unique identifier to distinguish the different import sessions from each other, available within the default template.
The width of checkbox fields should always be fixed.We believe, making the width variable and depend on the total available width makes no sense. Unwanted behavior in a FormList scenario:
I think that it would be good if we would be able to specify database timeouts on both a global and a more detailed view / subject / task level.I posted this as a question before; Sometimes things can end up running so long in the background that the user won’t wait for them anymore, I think that it would be good if we would be able to set a general timeout for all views, and queries. Next to this it would be good to set a larger timeout for some tasks and specific views, as some things could take longer than “normal”.
It would be helpfull if I could decide the task variant my process flow uses as a start object when using a table task. It is possible for the ‘start task’ but not for the ‘start table task’ process action. I want to use this to implement different task behaviour per table variant:
Currently there is no way to assure that a role (or user group) should not co-exist (within a user or user group) with another role.For example one user should not be able to create a credit invoice and pay the same credit invoice. In some cases you want this to be done by separate people within the business.It would be good to be able to create a matrix of roles that should not be assigned to the same user or user group.When a user tries to assign an illegal combination of roles to a group or a user (due to a combination of groups) IAM should not let you and give a warning.
In many ways the new database event log is a big improvement but I am encountering that the new overview isn't showing the request parameters, thus making finding the request I'm looking for more hassle than needed.Also there is an request ID in the database event log but this ID isn't available in the HTTP response, so relating a HTTP response directly to an event log isn’t possible (only assumptions based on time etc) It would be very nice to be able to always show or at the very least make it possible to enable showing the request parameters in the new log and to add the RequestID to the HTTP response headers thus making the relation 100% clear (and searchable!) Example:Event logNetwork Relation between these requests is only possible based on assumptions and this is the simplest example I can create, most situations are a lot more complicated.
The text in the dialog box of tasks is too technical for the user. Do you want to execute task Undo approved declaration should be “Do you want to undo approved declaration.” Execute task does not add anything for a typical user.
In the pivot of my cube it is possible to turn on grand totals, however, it is not visible in the chart. It would be nice if the grand total data also becomes available in the chart. As a work-around, the data in the picture below is calculated as a sum in a union for my view. This is not ideal because it cannot be filtered and this data will also be added to the original grand total.
Hi. There is a PDF merge action. I really am looking for a PDF splitter at the moment. Can a splitter be added? Basically I have various PDF's of 50-100 pages and I only need certain pages, which are made known via page-ranges. Like 4-7,9,11-12
Currently it is not possible to show 2 different subjects on 1 page. In order to do this, you have to create a reference between page and remove all the reference columns. This is not the most logical and best looking way to implement this.Since this is asked for by my clients quite often, I think it would be great if we could set up something to configure this in the SF without having to apply this workaround.
For columns with invalid information we want a red background. When applying this to date_from and date_until we have a single condition, but want to apply it to both columns.In the current situation we have to create a conditional layout for each column and each set of AND-conditions. It is very easy to make a mistake here, especially when there are a lot of combinations.An improvement would be to have the option to add multiple columns to a Conditional layout.
When using a Cardlist the columns are not responsive. Example if you have a description of a product of say 70 characters and you use a small size screen that you would want the descrption to be displayed over two lines. Now the last characters are not visible.Now it’s not responsive
To make certain forms more user-friendly, I’d like to be able to use the well-known ‘switch’ as a control.It would behave exactly the same as a checkbox, just have different visuals (and be placed on the right instead of the left of the label).You can find examples in your Android or IOS system settings, where the switches show on certain settings on the right side. Bootstrap example: https://getbootstrap.com/docs/5.1/forms/checks-radios/#switches offonThe ‘on’ color could be set to the accent color set in the theme.
We have a few indexes in our application where due to the keys and ordering it is required to adjust the fill rates of the index to avoid instantaneous fragmentation when any record is added. Currently we have solved this with some after upgrade scripts but it would be convenient to be able to set this as a parameter on the index within the SF model.
Currently, the OAuth User Login connector within Thinkwise always requires the use of PKCE (Proof Key for Code Exchange). While PKCE is a secure method for protecting the authorization code exchange, there are still OAuth servers and systems that do not support this method. This can pose challenges for integrations where PKCE support is unavailable. To facilitate integration with such systems, it would be beneficial if Thinkwise provided the option to enable or disable PKCE based on the server configuration. This would increase flexibility and help simplify integrations with various OAuth servers.
I have some system flows with more steps. If there is an issue with the system flow, it’s hardly undoable to debug. There’s no logging at all. I now created some logging in the application self, but with steps with no code attached it’s not possible to track the system flow in the debugger somewhere.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.