Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Please create a separate role for access to the error log so that developers don’t need to become main administrator to access it. For reference: Could Debug center access to Error log do with lesser rights than Main Administrator? | Thinkwise Community
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.
When creating a new column with domain elements you have to set the control to a type that can work with domain elements (like combo). If the control is not combo lookups using this domain won’t work properly in universal. However, why would you want to use domain elements without combo (or the other options like radio button and checkbox)? I would argue combo is the most used option. There is a validation for this, but I would opt to setting the value to combo by default, and the user can always deviate from this. To make the SF user friendlier and less complex. When you add a domain element and the control is empty set the control to combo instead.
I've been playing a bit with Custom components and it's great and powerful, but it would be nice to have some info on authorizations so if we add a delete button for example we can upfront check if the logged in user can actually use it.
Having the possibility to use indicium to automate generating / unit test / validation and all is very nice, as found here: https://docs.thinkwisesoftware.com/docs/sf/deployment_automationI think it would be a great addition the be able to schedule these from within the SF since from there we know the current project / project_vrs and the indicium we need.We want to schedule unit test and validations every night, it would be nice and quick if we can accomplish this within the SF with a simple click instead of having an external program running a schedule and retrieving the current active project_vrs to run the procedure.
Hello everyone,I am in a situation where it would be super useful to create a task, and then use a process flow to change prefilters. But that can only be done using the main table. In my situation I have a few lanes with a variant of a table on each lane, and only the first lane responds to the changing filter. This is unfortunate, because now I have to solve this issue vastly differently and makes things, code and maintenancewise, a lot more complex. This is what I would like to see: I think it would be quite use ful to have a variant column beneath table as in some of the other options where you can pick a variant.
Can the configuration under User Preferences to set Start Objects also be made available in the Universal GUI, as it is in the Windows GUI?
We would like to have the ability to assign a custom schedule to the unit tests within the Software Factory, so they can run as frequently as we need. Running all unit tests for every creation is no longer feasible, as we now have nearly 500 tests and the full suite takes more than fifteen minutes to complete.At the moment, we have solved this ourselves by creating a SQL Server Agent job that triggers the Software Factory task responsible for executing all unit tests. We are very happy with this solution, as it allows us to run all the unit tests every night.Several times already, the nightly run has revealed failing tests caused by code changes made the day before. Because we caught these issues early, we were able to resolve them quickly, ensuring that our sprint delivery was never at risk.Now that we have this setup and are very pleased with the results, we can easily imagine that other teams or companies who rely on regression testing would also benefit greatly from such a feature.
Hello,I am working on a drag and drop interaction and I want to achieve the following:When dropped on a row the dropped item needs to be added to the row in question When dropped in the empty area the item needs to create a new row and add itself to it. Now i have the drop on row functioning correctly if i drop it on the row i get the parameter of the target and source which i can use in my code. But when a row is present in the target table and i drop outside of a row i still get the target parameter which makes it impossible to detect in my code if im dropping on empty or dropping on row. Drop on rowGets the parameter Drop outside of the rowStill gets the parameter :(Is it possible to achieve the desired behaviour? (to detect if a row is dropped on a row or on empty space?)Kind regardsAnne Vries
When you make alterations to the model, especially the data part that results in an upgrade script, there a plenty scenarios that break at actual upgrade. Especially for new users, because it's not always that obvious.I would like to see the SF dealing with this scenario more elegant. And it should be not that hard to offer some kind of rollback. Because all the info is there to upgrade, so also all the info is there to return to start. I am thinking about:Making especially the upgrade part interactive. Especially to have before the deletion of the temporary tables the choice to delete or rollback, in case of any error occurred. Or perhaps a separate task to reinstate the original tables, so you can fix whatever went wrong in the model and rerun the upgrade.Now you have to 'hack' your way through it via SMSS or go for restoring a backup. Which would also be a good and probably simple addition to the SF. Every upgrade should have the option to automatically create a backup before execution.
On subjects with many tasks, it is hard for the user to find the right task in the universal GUI. It is also impossible to show the tasks with name on the screen because it will never fit (and we don't want to put alsmost everything in the overflow menu).Adding a task group doesn’t really help since it only creates a splitter. Please add support for task-group sub menu to the universal GUI so that we can create a drop down with tasks. Example (this subject even has more tasks in the overflow menu and hidden by context):
Subflows are a great addition to the Platform in order to re-use parts of a Process Flow, instead of having to model the same set of Process Actions in multiple Process Flows. Subflows improve the re-usability of components, therefore we are eager to use this concept in regular Process Flows too!Can this functionality be extended to be available not only for System Flows, but also for regular Process Flows?
Is there a way to set the treeview row height?I was expecting the same height as the grid row height, but the treeview remains higher.
It would be nice if table valued functions could be used as a lookup for a task. So the lookup changes dynamically with the input given. For example:I want to limit the delivery weeks for a customer to choose from, depending on the delivery week of the active line the user is on. So if the user is on delivery week 202550, i want the ability to show the possible deliveryweeks 202548 till 202552 for example. A table values function could return this, based on the input param 202550. If there is another way of doing this, please let me know, but I can’t find it.Thanks in advance for the reply :-)Grtz, Gideon
When adding or updating a record I often find myself in a situation where I would like the selection (combo lookup) of field C to be filtered based on values I have set in fields A and B. Currently the Software Factory only allows you to create such a behavior when you include fields A and B to the lookup reference column list. This poses a bit of an issue when for example you would like to filtered based upon a date field.There is a better way to create such behavior. If the Software Factory would allow you to determine the lookup combo values based upon a tabled value function. You could then include the values of fields A and B into the parameter set of the function.
We regularly see expression columns or prefilter with heavy constructs that effect the performance. So it would be nice if we can review expression columns and prefilter just like control procedures. Which would include the following features: · Approve/disapprove prefilters and expression columns · Add comments when disapproving prefilters and expression columns
In the past, when we used the WebGUI, we used the IAM Action Analysis. After switching to the Universal GUI we can't get any data from the Action Analysis in the IAM. For us, as a ISV, it is valuable for us to know how our application is used by our customers and users.
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