Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
The pivot tables (Cubes) have come a long way and if I understand correctly, they are still under development. I have encountered some scenarios where I had the need for a more dynamic grid. In some scenarios we used views as a complicated work around, where the headers and amount of columns are fixed, and in the first row we create our own headers and we pivot the data in the query. Of course a sub optimal solution. In other scenarios we used the grid + grouping as an alternative, so data is shown close to each otherAs a practical example:In a proof of concept, a customer wants to compare the texts of different contracts per subject and per supplier.The ideal situation would be to have the suppliers on one axis and the subject on the otherthe specific text of each subject / supplier would be visible in a cell.In a pivot table in Excel and in Power BI it is perfectly possible to use a string for the data. It simple demonstrates the text or counts the amount of entries. I noticed that the cube of Thinkwise can only handle numeric fields. If the cube could handle strings as well this could be very valuable to create matrixes like the one I mentioned.Do you think this is technically viable? Or do you see other possibilities that I'm missing?
I would like to be able to select items in the treeview like the custom screen ‘Generate source code’ (manually). The default behavior could be the same as ‘Generate source code’, but it would be great if we could model a type of behavior.
Is it not possible to add https://subdomain.domain/indicium/ as prefix to the URL in the Database event log? If there are any security concerns, only when running in SF / Developement mode is fine.This would help a lot during the development process.
As a follow up on this conversation: it would be great if there would be a simple way to create multiple custom login screens for the same Application and Infrastructure. This way we could differentiate login flows for different ‘types’ of users in our organization (as a direct customer of Thinkwise), for example:Internal users with Azure AD account are automatically redirected to the Microsoft login screen, specific for our Tenant in order to ensure our MFA/Conditional Access policies Internal users without an Azure AD account are automatically redirected to the Local login screen External users with a generic registration at Microsoft / Google are automatically redirected to the login screen with both Microsoft (common) and Google as login optionsIn addition, I believe this could be of great added value for ISV's as well, whereby they can offer their customers the ability to use a tailored Login screen and use their customer-specific OpenID provider.Having to run multiple IAM databases kinda destroys the idea of Intelligent (centralized) user/Application Management and is overkill for such a relatively small-scoped feature.
Currently we have 4 sites running the Thinkwsie Web GUI (not counting Test and Acceptation servers). They all run on the same IIS server and based on the directory in the URL one of the GUI's is selected. This means four installations each time a new version of the GUI comes available. Now my organisation wants even more variations, and the only thing that is different is the sitename (which each time is translated to the same IP address, thus the same server). If it were possible to distinguish betwewen what settings to use based on the sitename, only one installation of the GUI would suffice, meaning less resources used by the server, less installation time when a new GUI is rolled out by Thinkwise etc etc. Example using 4 URL (=4 different IP adresses all pointing to the same IIS Server); https://portal.CompanyAlpha.com/guiAlpha https://portal.CompanyBravo.com/guiBravo https://portal.CompanyCharlie.com/guiCharlie https://portal.CompanyDelta.com/guiDelta This means 4 GUI installations on the IIS Server, when each company want their own "Look & Feel" of the GUI's login page. When the same user, me for instance, logs on, he of she will see exactly the same available applications after validation of the username and password. But not all users see all applications, so the desire to have a different login page per company is valid. Example settings.ini with mutiple sitenames (how Thinkwise implements my suggestion is open for discussion, it's the idea that counts ; First the default settings when no "sites" are configured in this INI file ; IAMmetasource = iamserver = SQL006-DBDMS.xxxholding.localdatabase = COMP_IAM_PRODrdbms = sqlserver ; MiscLogToFile = yeslanguage = nlauthentication = rdbms Application_login_logo = I:\Thinkwise\logos\login_logo_default.jpgApplication_title = Whatever you desireBrowsericon = I:\Thinkwise\\icons\favicon.ico ; Other settingsallowResetPassword = yesSmtpServer = mycompany-com.mail.protection.outlook.comSmtpFrom = noreply@mycompany.com ; Site dependant settings ; CompanyAlpha deviations[sites][portal.CompanyAlpha.com]metasource = iam[sites][portal.CompanyAlpha.com]server = SQL006-DBDMS.xxxholding.local[sites][portal.CompanyAlpha.com]database = COMP_IAM_PROD[sites][portal.CompanyAlpha.com]LogToFile = yes[sites][portal.CompanyAlpha.com]language = de[sites][portal.CompanyAlpha.com]authentication = rdbms[sites][portal.CompanyAlpha.com]Application_login_logo = I:\Thinkwise\logos\login_logo_Alpha.jpg[sites][portal.CompanyAlpha.com]Application_title = Bookings Application[sites][portal.CompanyAlpha.com]Browsericon = I:\Thinkwise\\icons\favicon_Alpha.ico[sites][portal.CompanyAlpha.com]allowResetPassword = yes[sites][portal.CompanyAlpha.com]SmtpServer = mycompany-com.mail.protection.outlook.com[sites][portal.CompanyAlpha.com]SmtpFrom = noreply@CompanyAlpha.com ; CompanyBravo deviations[sites][portal.CompanyBravo.com]metasource = iam[sites][portal.CompanyBravo.com]server = SQL006-DBDMS.xxxholding.local[sites][portal.CompanyBravo.com]database = COMP_IAM_DEMO[sites][portal.CompanyBravo.com]LogToFile = yes[sites][portal.CompanyBravo.com]language = de[sites][portal.CompanyBravo.com]authentication = rdbms[sites][portal.CompanyBravo.com]Application_login_logo = I:\Thinkwise\logos\login_logo_Bravo.jpg[sites][portal.CompanyBravo.com]Application_title = Bookings Application[sites][portal.CompanyBravo.com]Browsericon = I:\Thinkwise\\icons\favicon_Bravo.ico[sites][portal.CompanyBravo.com]allowResetPassword = yes[sites][portal.CompanyBravo.com]SmtpServer = mycompany-com.mail.protection.outlook.com[sites][portal.CompanyBravo.com]SmtpFrom = noreply@CompanyBravo.com When this is implemented, I could suffice with installing just one GUI and point all sites to the same directory, like: https://portal.CompanyAlpha.com/thinkwiseGUI https://portal.CompanyBravo.com/thinkwiseGUI https://portal.CompanyCharlie.com/thinkwiseGUIhttps://portal.CompanyDelta.com/thinkwiseGUI
When you have a scroll bar on the menu of the universal GUI, the search field becomes hidden when you scroll down. Could the search field please become locked so when you scroll down in the menu, you always have direct access to the search field?
Can the search and open document always be visible on top, also when you are scrolling down.In Windows GUI, the search is at least always visible, in Universal GUI all disappears when scrolling down in the menu
Description:Allow screen titles in Universal GUI to be either clickable or accompanied by a help icon that links to external documentation.Rationale:Users often need contextual help. Linking screen titles to external resources improves onboarding and empowers users to find answers independently. Suggested Implementation:Add a configuration option in the Software Factory to define a URL per screen. Display a help icon (e.g., ℹ️) next to the screen title, which opens the link in a new tab.Optionally allow the title itself to be clickable if preferred.
When searching a menu item the search value stays until you manually clear the field. Can we make this like the windows gui? Where after selecting an item from the menu the search bar is cleared, this would reduce the amount of clicks needed to continue your work. After clicking contacts:
Being able to use a wizard that, for example, gives the user a tour of how to use the application. This should appear as a pop-up balloon with the necessary explanation of a button or function
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK