Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
For an image-upload control, it is currently not possible to disable the hyperlink/download feature in the form (read mode).It is annoying that clicking anywhere on the field opens a new browser tab with the image while the user is never interested in downloading the image in this case.In the example below, the image field is the full width of the page, so clicking anywhere right of the actual image opens a browser tab with the image.The GUI could maybe use the domain ‘Show action button’ setting to configure this behaviour. An alternative could be that the GUI is changed so that not the whole image field is the button, but that images get an small action button in the corner as is done with other type of controls.
Currently, the drag-and-drop function works by dragging one record onto another. The second record is the only drop target data available for determining the subsequent actions.It would be more intuitive if the drop behavior worked like in most applications, where a thick line is displayed between two rows in the UI to indicate where the record will be placed.From a technical perspective, the result could always return the row data of the record directly above the line (or an empty value when the record is dropped at the top). Alternatively, it could return the data of both surrounding rows.
I would like to be able to set a handler specific for a copy action that also uses the source row primary key as parameter(s). This way we do not need to create a specific copy task every time we want to include weak-entities in the copy action but the handler can execute that logic.This also has the advantage that the copy action is always at the same position in the action bar.
Can you change something on the visibility of the inactive TABS. In the WIN GUI the colored Icons were made grey on an inactive tab. When the tab was active the colored icon was shown. So it was very clear for users when the tab was inactive. And with using color it was also very clear when the tab was active.In the current Universal version the inactive tab is shown with very lightly reduced colors. As wel the text of the tab as the icon. This is the inactive variant And this is the active variant. When you see them here in exploded format and next to each other the difference can be seen. However in the application you see one or the other, and they are much smaller. So for the user it’s much harder to see if the tab is active or not.The grey variant for the inactive variant in the WIN GUI was much and much better and much more clear to the user
Having countless of program object types makes it kind of a pain for filtering when dealing with merge conflicts (especially merge sessions with numerous conflicts). Long long list of object typesIn my instance I know a majority from the conflicts originate from Translations. Now I have to manually scroll all the way down to the ‘T’ area and still look around there. Would be nice if I could just type and search instead.
I want to use generative AI to draft the bulk of my SQL templates, directly from my own IDE (e.g., VS Code) together with tools like GitHub Copilot. For this to work reliably, the AI needs first-class context from the Thinkwise Software Factory (SF): the application’s model metadata and relevant UI information. The SF already maintains a rich, structured model of tables, columns, and references; exposing that to the AI is the missing piece.Why this metadata is essential for AI-assisted SQL When the AI understands my model, its output stops being generic and becomes project-specific:Tables, columns, PK/FKs – enable correct JOINs, WHERE clauses, and integrity-awareness. The SF’s data model explicitly defines these entities and relations, which the AI can use to pick the right join keys, respect cardinalities, and avoid hallucinated columns. Domains (user-defined data types) – domains act as abstract data types that drive constraints and UI defaults. Sharing domains helps the AI choose correct data types, casts, default values, and validation logic in generated SQL. UI semantics – properties like control type or visibility can guide the AI to prefer filtered queries (e.g., hide inactive rows by default) or to shape parameter prompts and WHERE clauses that match what end-users actually see. Template description & intent – short, descriptive text per template (purpose, invariants, edge cases) gives the AI the business intent it needs to generate more accurate and consistent code.How I propose to make this work Expose a compact model export for use in VS Code MVP scope: tables, columns (incl. nullability), primary keys, foreign keys, domains (name, base type, constraints). Optional scope: UI hints (visibility, control), default filters, and template descriptions. Delivery options (any of these would work): Indicium OData endpoint that surfaces a read-only view of the SF model (Indicium already provides an open API and can expose SF branches when configured). CLI/export task that writes JSON files into a repository (consumed by VS Code). VS Code extension that authenticates to the endpoint and injects the model as inline context for Copilot prompts. Use the model export as AI context in the IDE In VS Code, I want to select a template and have the AI read the JSON/endpoint to generate the initial SQL ready for review and refinement. Expected resultsSpeed: AI drafts 70–90% of the SQL, I focus on edge cases. Quality: Consistent use of keys, domains, and defaults; fewer “missing join” or “wrong column” errors. Discoverability: As Thinkwise continues to add AI-powered features (e.g., model enrichments and support for storing LLM embeddings), a model-aware export aligns with that trajectory. Future fit: Community use cases already show value in combining Thinkwise models with LLMs (e.g., natural-language search using embeddings), reinforcing the need for structured model access.
As per the Roadmap it was mentioned like 2-3 months ago that the HELP(F1) feature in the WEB GUI is in the backlog to be transfered to Universal. Right now the HELP(F1) is completely gone from the Roadmap. Raising the IDEA to have it in Universal upon receiving the relevant Votes.
Be able to assign a quick button to take you directly to "Search". For example assign "F1" button, when pressed, to take you to "Search"
This idea originally comes from @Harm Horstman, who suggested it in: Right now, Model Insights shows you what you're looking at, but you still have to find it in the Software Factory yourself. Deep links would remove that step and make the jump from runtime to SF instant. The ideaAdd a button next to the copy to clipboard button to all relevant items in Model Insights. Clicking it takes you directly to that object in the Software Factory, such as a table, domain, task, screentype etc.
I would like to see the Model Insights window to be variable in size. We use very long names and can only see the first part of it.For example:
When you have assigned rights to a column that has a lookup and later you change the lookup display column, the column becomes unavailable and effectively has no rights anymore. I made a validation to detect columns with lookups that have rights but are unavailable, please add this to the validation basemodel.--Lookup has rights, but is not availableselect rco.* from role_tab rt join role_col_overview rco on rco.model_id = rt.model_id and rco.branch_id = rt.branch_id and rco.role_id = rt.role_id and rco.tab_id = rt.tab_id where rt.model_id = @model_id and rt.branch_id = @branch_id and rt.select_granted = 1 -- own table has rights and rco.col_access_type in (0, 1) --0=edit, 1=read only, 3=hidden and rco.available = 0 and rco.look_up_source_tab_id is not null and rco.sf_type_of_col <> 3 -- meta hidden fieldWhat also could be considered is to automatically assign rights when changing a lookup display column that previously had rights.
When we do our upgrades (every 3 weeks) of our applications we take the application offline (deactivate in IAM) right before we execute the source code on the database and we put it back online after the IAM sync.However as time goes on our model grows and the IAM sync action in SF is taking up to 8min right now, the majority of that time goes into generating the sync code. If we could generate the sync code separately from the actual sync this would decrease the required downtime for upgrades by a big percentage because you could generate the sync code before taking the application offline. On top of that it is pretty easy to forget to do an IAM sync, it would be nice to have it part of the creation process/screen.
In the mobile-GUI the filter-field automatic gets focus.In the Universal-GUI no field has focus. By setting the focus to the filter-field, the user can use a barcodescanner to enter data (without first having to give focus to the field).
A use case that happens ins many cases is where you have the grid with a detail tab with the form and other elements. For the user It's quite cumbersome to be going back and forth every time he wants to see the details of a couple of items in a row. I really miss the previous and next navigation buttons in the detail, where you can jump easily to the next or previous item in the context without the need to go back.
Via the Windows GUI it was possible to create onw prefilters, which were on “by default” (if on at last use, then these were on next time view was opened).Would be fine to have this option available again
As discussed in topic:Also the users of my clients are requesting for more contrast between the selection and the non selected lines.It would be great if we can have some impact on this. A css solution is also acceptable, not ideal.
Most core applications have quite an extensive menu, easily creating a scrollbar for the menu, specially on smaller screens. When scrolling down, you lose sight of the Search field and Open documents which is quite annoying.Therefor I suggest to make it possible for a user to pin down the Search field, the Open documents and the Favorites (each with their own setting) so that they stay locked on the screen and don’t disappear when you scroll down in the menu. This settings should be saved as a user preference.I’d say the search field could be pinned down by default.
Smoke tests are running very long in a model ± > 300 tables. if you want to run for test. If it’s possible to execute the same tests for a selection of tables/views its easier to check changes to primary key of one table for example. Check mandetory fields in views as well.
It would be very helpful ifyou can always add info to a ticket, also when it is processing (e.g. when you want to add some info / inform to close ticket). Now you don't have this option (buttons are disabled) to assess a solution, there is only an option to add comment in case you don't accept. But when you accept, it might be useful to add info (got give extra feedback to TW)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.