Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
With SF 2026.1 some changes were made with the use of auto-edit and auto-save on different subjects, but I feel like more screens could be improved with the use of auto-save on grids.For example: -Data model - Tables - Columns-Functionality - Templates-Roles - All detail tabs-Subjects - Columns, this is currently on auto-edit but since there is a form to edit and the only editable field in the grid is ‘type’, auto-edit is more confusing then helpful here. So I think auto-save would be better.-… basically everything that is edited through grids.
When I use the scheduler, I can set the date in the date picker or I can scroll in time. When I start a task for a resource, I would like to know the value of the selected date.
We need more options to set up the time scales in the scheduler to see more details per day.Currently, the possibilities are too limited, and the behavior is not as expected.Time scale options in the software factory make it seem possible, but the end result looks very different and some combinations do not even work. We need additional options like these. It is also desirable to be able to set that the current date is on the left side of the screen when starting See also here:
The sliding scale selector is nice,, but I would like it to have a popup to go to a more distant date more quickly. Or even some smart buttons here to go the previous / next event… Scheduler always starts on current date, and I would definitely prefer if the system does that only when there is no activity planned yet.. in all other cases it should go the first activity planned.
The current scheduler always start on the current time. This is unwanted. I want to be able to programmatically set the start date. There are a few ideas around this concept:Overrule start-view with custom date. Bound the plan-scale with start / end-date (for example when you plan an event) Hide non functional days/hours (holidays, weekends or other defined dates.. and hours that cannot be planned… )
In case only one tenant exists it would help to create default rows in these tables when a web domain is added: :web_domain_allowed_tenantweb_domain_login_optionElse nobody will be abble to open the application and there is no other way to solve the problem via the IAM database
For a customer I have created a scheduler in Universal. However, the customer indicates that she would like to set working days and working hours. This means that in certain scheduler views some end users have to scroll a lot to see the desired results. In the Windows scheduler it is possible to set working days and working hours. Could this setting also be applied to the Universal scheduler? This would be an additional reason for the customer to switch to Universal (earlier).
In the Resource Scheduler for the Universal GUI it would be handy to enter a start and end time for a day, so that not all the hours of a day are shown in the scheduler? For example, for suppressing night hours.
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
We use a lot of Modal document form in our application, which works great. There are however some situation where a process flow end with the opened document. After a user is done with the required actions we sometimes desire to take care of certain actions after or triggered by a closing of the document.Unfortunately this Action does not count as a starting point.A workaround for now is using a task in the screen that follows with a “Close document”, but the user often misses that. The “CLOSE’ button takes so much focus, that such a task would be missed. Also if the screen already has many tasks, it would not stand out that much anyway even when marked as primary. The idea is to make “Close document” a starting action in a process flow.The idea of course goes with a warning that the “Close” is always available on such a document, that one should be aware it could be pressed without actively having done anything in the screen and uses it as a cancel, but I think this should be the responsibility of the developer using such flows.
Since Universal GUI 2025.2.13 (rc1) fields with ‘Look-up has popup’ will become clickable in the (non-edit-mode) grid to open the lookup. This is a great feature, however not in all cases is this desirable.There can be multiple reasons to use a lookup popup in edit mode to help the user find the right record, but this doesn’t mean that it always adds value to open the lookup in non-edit-mode. Having many lookup fields in a grid can make the grid feel troubled and I also can imagine it could conflict with setting up a double click task on lookup column.So please make it configurable for (non-edit-mode) grids which look-up field are clickable (to differentiate from the edit-mode). For example under Subjects > Components > Grid.
I'd like to be able to make a Variant of a Domain with Elements. Instead of making 'close to double' Domains I'd like to be able to do the next: Domain: "document_types" Elements(just some examples): 1- Purchase Order 2- Sales Order 3- Invoice 4- Picture 5- Kick off Document 6- Financial Summary So the case would be: I have a Documents table with a column "document_types" with this domain. As example there will be 2 views, where you can add Documents on different ways. So view 1: I want to be able to add Purchase Orders, Sales orders and Financial Summaries and in view 2: I want to be able to add Invoices, Pictures, Kick off Document and Financial Summaries. To achieve this i would have to make 2 more domains for view 1 and 2 where I'll also have to make sure the database values are the same as in domain "document_types". Right now it takes: -1 Extra time -2 The maintainability of these columns/domains are harder, because you need to make sure they are in-line with each other. What do you guys think?
At this moment, only one instance of a task can be linked to a table.
Now that history data has its own data mapping for data migration, please use the same default value as the field itself has a default value.So for example a mandatory checkbox field that has a default value of 0 in the col table: in the datamigration mapping it already inherits the default value value for itself. But the default value for the history data stays empty right now.
I would like to propose an improvement (or ask for help) regarding the Activate Detail event when used as a Start Object for a Process Flow.I want to use the Activate detail event to trigger a Process Flow. The goal is to fetch data from an external system/API and display it in the detail screen only at the exact moment the user opens that specific tab.Currently, when the detail grid is initially empty (no records), the Process Flow triggers successfully, but the input parameters are empty. The flow does not receive the Primary Keys (PKs) from the parent/reference record.Because of this, the Process Flow executes, but I have no context (Foreign Keys) to determine for which parent record I need to fetch the data.This behavior seems inconsistent compared to a Table Task. When you execute a Table Task on an empty detail screen, the application does pass the PKs from the reference/parent record into the task.I haven't found a way to retrieve the parent context in this specific scenario.If I am missing a configuration setting to pass the reference columns to the flow on an empty grid?Consider this idea to enable the Activate Detail event to receive the reference columns/parent PKs as input variables, even when the detail grid itself is empty.
It would be a good idea to validate at the moment you add Elements to a domain, that the length of the domain is sufficient to store the element database value.For example:Domain will be added with data type VARCHAR, length 5.Element with database value "TestValue” will be added.The system alerts the developer that it’s not possible to add this value as it would not fit within the domain setting of max. 5 characters.This would avoid frustration at testing when the developer notices that it’s inpossible to store the full database value "TestValue”.
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.
Recently Microsoft introduced the latest version of SSMS that supports a new feature, Database Instructions, that allows you to store instructions and database structure information in extended properties.Database Instructions - GitHub Copilot in SQL Server Management Studio (Preview) | Microsoft Learn We use SSMS as our IDE combined with Github Copilot and having this integrated into SF would make this even more powerful.
In the Universal GUI grid the selected row, and the selected rows in multi-row selection, have different shades. Sometimes it's hard to tell which rows are selected. Currently these colors cannot be changed.It would be nice if this was configurable in the Software Factory.
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