Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
The current state of the Thinkwise platform is really close for creating Wizard functionality in which you guide the user through specific steps. You can already create a task that triggers a process flow that opens another task or that opens a modal document (for letting the user enter data in a grid). However when using a modal document in a wizard like functionality, some essential points are missing to make it a complete wizard (with the use of multiple process flows):Closing the modal document should be able to trigger a new process flow (for the next step in the wizard or to refresh the underlying document). It should be possible to use a custom translation for the ‘Close’ button of the modal document (same as recently was done with task buttons). You could for example rename it to ‘Next’ or ‘Continue’ and let a process flow open a new modal document or task.Optionally, the following functionality would make it even more flexible so that you could use your own tasks (multiple) for guiding the user through the wizard:Make the ‘Close document’ process action also work on a modal document (that was not opened from the same process flow).
Thinkwise Guideline validations (found in the Thinkstore) are an important tool for improving the quality and consistency of our models. They help developers follow best practices and highlight potential issues early in the process.Currently, these validations are available in the Thinkstore, but they need to be manually added to each project. This increases the chance that teams don’t use them, missing out on valuable guidance.By including these validations by default in every new project, we make sure all projects start with the same important checks in place, helping teams build better, more maintainable applications from day one.
In Grid row height in Universal differs | Thinkwise Community Erwin explained that a smaller grid row height (for example 22px) will be overruled when it is possible to edit in grid because the editor needs the room.This is really unwanted behaviour because it prevent us in showing better data densities in our applications.So please make it possible to use smaller grid heights when edit in grid is enabled. It would be fine if just the row that is being added/edited temporary grows in size for the editor functionality to function properly.
We need to set a global setting to set the header label to stay small and not to move to the location where the field is. Similar to having a field with an empty value (not a NULL value).
This Idea is more or less a follow up on the Idea regarding the Universal GUI zoom. The Compact mode has significantly improved the ability to properly work with the Universal GUI, however it is still a challenge to display a sufficient amount of data on a single screen in the Universal GUI for a data-rich ERP system, due to the large amount of white-space/padding/… around both Grid and Form controls.The Universal GUI Forecast has planned something for reducing the Grid line height and font size, but I would like to argue that the width of the Grid columns could be reduced as well.Grid line height and font size settingsThis will allow for custom settings for the grid line and font sizes. These settings are only used by compact mode for this first iteration! In addition to Grid changes, this Idea aims for similar reductions on Forms and potentially other Screen Types.
It would be a QOL update for the Universal GUI to be able to scroll through detail tabs.When there are many detail tabs, it would be nice to use the mouse wheel to scroll left or right. Now you have to click on the arrows on the side. When using a mobile device, you can drag the details with your finger. This is also not possible with a mouse (click and drag).
We are not using prefixes for layouts/defaults/contexts in our stored procedure names (we use suffix), so it is annoying that the SF default enters the wrong code group. Please create a setting to turn off this default. For reference: SF: turn off default code group | Thinkwise Community
Small QoL improvement to increase productivity for (sub)processflow management in the SF:Please create a detail tab behind processflows with a view of all subflows used in the processflow. It would be nice if adding in the view would be possible and that an insert means creating the subflow + creating process action to execute it. The view should have the same details as the subflow window (which should be editable). I know it is already possible to use the subflow lookup to view/edit the subflow, but this is too far away (too many clicks required + harder to switch between sub flows). Context: For most system flows we also have a task so the user is able to trigger it manually. This forces us to place the logic in a subflow and use two process flows to trigger it (one with the task and the other with the system flow schedule). When a develop wants to do maintenance on any of these flows, he instinctively first opens the process flow screen only to find out he needs to go to the subflow screen instead. So it would be easier if he could just click on the subflow detail tab.
To improve the quality and maintainability of applications, Thinkwise should provide a project-level option to make all description fields mandatory (tables, columns, domains, references, datamodel diagrams, tasks, etc.). (This means it will be an optional feature you can enable as a project team).This ensures that developers think about why they are creating something and provide proper documentation during development. To prevent abuse, the feature should also support validation rules so that meaningless inputs (like just entering "." or "test") are not accepted.With this in place, descriptions become a real part of the development process, improving collaboration, knowledge sharing, and long-term maintainability of projects.
I'm really enjoying the AI code review feature in the Thinkwise Software Factory—it’s been a great help in aligning our code with established standards.What I’d love to see next is the ability to define and apply our own custom rules within the AI review. This would allow us to maintain the specific standards and conventions we’ve developed internally.We’re not just looking to enforce simple line-level rules like:Each table should have an alias. Each alias should follow a logical abbreviation. Every object should use object qualification.We’d also like to define more context-aware rules based on settings or column patterns in the Software Factory. For example:For tables with an “active” column (e.g., table1, table2, table3), only active records should be selected. For tables with trace columns like update_user and update_date_time (e.g., table1, table2), these should be manually set in every update statement using tsf_user and sysdatetime.Ideally, we’d like a solution that allows us to add and manage these custom rules without them being overwritten during Software Factory upgrades.
I would like the possibility in Universal to make a conditional layout only visible on the form or grid. In the current situation, this always happens in both places, even if you have indicated this in the SF.
In the Software Factory, I would like to have the possibility to configure a View as an indexed view. Indexed views (when used appropriately and with care) can improve performance (just like indexes on tables). For more details: https://www.sqlservertutorial.net/sql-server-views/sql-server-indexed-view/
We wish there was a process flow action that could refresh active tables from other clients/users using a websocket protocol.Think of charts and dashboards that continuously display the latest status immediately, as soon as certain data is changed anywhere in the application, without having to poll.Like large screens that show departure and arrival times or order statuses and many other application in full-screen mode.
I would like to have more control over the way details open, specifically from a detail tile. I would like it to open as a floating screen for instance. Having the screen been modal (thus preventing the user from navigating away) would also be a great feature to have. In my case the users have a touchscreen interface so using the ‘alt’+click shortcut is not an option and is also not something I want to make the responsibility of the user. So far I’ve got two workarounds but neither are very elegant: Using ‘empty’ tasks instead of detail tiles and having them open the detail in a process flow, but this leads to clutter in the tasks and makes adding tiles a hassle, also it defeats the purpose of the tiles and leads to a disconnect in the styling of the icons for instance using a process flow to close the initial window and reopen it as a floating window, this is sluggish and also unnecessarily complex I would prefer to be able to do this in a simpler and faster manner, so far the following places where I would expect such a setting to be located are as follows, from likely to less likely: Handling the opening style within a single process action, for instance on the ‘zoom in on detail’ action type Specifying within the subject or subject variant Specifying for a reference Specifying for a screen type
For example, when I want to add a new entry, I can see the mandatory fields that are not inside a tab page:However, then I will save my entry and I get the following error: My issue is that I currently do not know if a tab page contains a mandatory field. Right now I can only find out by saving or manually open all tab pages to check if it contains a mandatory field.I see multiple options:Automatically open tab pages that contain mandatory fields which are empty. Mark a tab page with a red *, in the same way that is done on field level. Show a badge with a number of mandatory empty fields.
The SF/IAM databases are Case insensitve (Latin1_General_CI_AS) by default.As we sometimes make some mistakes (who doesn't), we'd like to correct the cases in translations.E.g. cange “Purchase order” to “Purchase Order”. Currently there are 2 workarounds:update the records in transl table or, change to “Purchase Order1”, sync to all IAM's and change to correct “Purchase Order” The idea we'd like to see implemented is that a collate Latin1_General_CS_AS compare takes place and also the update will take place in this collation so the correct cases will be stored.
I guess it should be possible to dynamically load a custom.css in the U-GUI via the model. So the custom CSS can be maintained from the SF.
As a developer I receive tickets from my clients about an issue in their application. When this is a GUI issue I need to submit a ticket in TCP for this and always have to include an .HAR file. It would be great to have a button “Download log file” in the User menu.And next to this I would also need the option to download a more technical file, including the Live error log information in a file.Both can be included in the same button which a user can use from within the Universal User menu.Having a button within the application to download these 2 debug files will increase troubleshooting and save a lot of time. Because you can instruct users, when they experience an issue, to download these files and provide them to you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.