Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When a finished branch gets merged to it's origin (non-reciprocal). It becomes finalized and, depending on selection, archived. Further merging into and from this branch is thereafter no longer possible. Yet, active development is still possible in a finalized branch (even after unarchiving). Wouldn't it make sense to completely lock development in a finalized branch as well? I have experienced a scenario where an unsuspecting developer was actively developing in a finalized branch (without knowing it was a finalized branch) and then find out way too late all of his work is for naught.
We would like to have the ability to show table tasks on a grid line. This is especially useful for the mobile GUI and when just a couple of table tasks are available. Currently you can show tasks on the top or bottom of a grid in mobile. To start a task for a specific record you should select a line first and then select the concerning task. In the described case it is faster to select the task direct on the line. See print screens for further explanation. Task on top of grid (current situation) Example tasks on grid line
As application managers / admins of a system it would be very helpful to know when a new user made their first login so you can assign them the correct rights. Having a push notification or alert come through would be a great way to achieve this.Please add a way to send push notifications for IAM to specific administrators in case of a provisioning event.
We would like to have an Excel-style filter in cubes, in the same way it works in grids.This is causing confusion with the users because the pivot grid in Universal looks so similar to a regular grid. Currently the only option is to open the filter pop-up, go to the column and use ‘in’, this is not really a viable alternative.
When working with the Windows GUI, you had a “...” addition to the action name when it would not execute immediately, but requires user input and then an “Execute” or equivalent button.Example of a task in the SF: Windows GUI with ...Universal GUI missing ...It is a nice indicator to see when a press of a button would run immediately or when you would have another input before that, meaning potentially cancelling available. Especially when an action could have significant impact, it would be nice to know how carefree the pressing of the button is.To improve this from the Windows GUI, make it also show the indicator when a confirm window is relevant. i.e. a Task with hidden parameters, but still has the “Ask confirmation” checked.
During development I regularly use the Windows GUI to find relevant information regarding screens, columns, parameters, etc. with the Alt + F1 combination (Path Location). Even though the Universal GUI has “Model Insight”, it is lacking many things the other option is giving.I think it is not the intent of ThinkWise to keep the need for using a different GUI to make your Universal GUI product complete. This idea is to make the “Model Insight” improve its usability and hopefully remove the need for a fall back GUI.Current issues or features missing that I am aware of:References more than 1 level deep, do still show the level 1 reference; References more than 1 level deep, do not show table / variant information; Unable to get info when a grid has no records to click on; No context information (Detail, Master, etc.); No Tab Control (What Detail group is being used); No Domain information; No Task name is mentioned, only the parameter as “Column”; No Report name is mentioned, only the parameter as “Column”; Lookup popups give no information, it still show the column/parameter of what it is a lookup on; No Translations.
The title might be a bit cryptic, but found certain tabs disabled until a record exists in a grid. A few examples are, in my opinion, a bit unnecessary.Data Model → Columns → Copy columnsI need to add one column before I get access to copy columns. There are situation where even my my first column is existing in another source and the copy would benefit me.Subjects → → Data → Prefilters → Prefilter groupsAs we use prefilter groups a lot, it is more fitting to create those first before starting the prefilters.Subjects → → Links → Tasks → Task groupsSimilar reason as for prefilter groupsSubjects → → Links → Reports → Report groupsSimilar reason as for prefilter groupsThe lasts three also make it impossible to delete an unused “group” when you have no prerequisite available anymore,There are probably more screens that could benefit from this idea, but at least these examples are an occurrence in my daily activity.
DescriptionWhen I delete an object in the Software Factory, any validation messages related to that object remain in the validation list. To get rid of them, I have to manually re-validate that specific item — an extra step that shouldn't be necessary.A concrete example: I have an "unused domain" validation message. I delete the domain to resolve it. But the validation message stays in the list until I explicitly re-validate the domain — which no longer exists. The message is now stale, but I still have to actively dismiss it.Desired behaviorWhen an SF object is deleted, its associated validation messages are automatically removed from the validation list — no re-validation required.Why does this matter?Validation results are a snapshot in time. Ideally, they would always be fully up to date. This request is a small step in that direction: when you delete something, the messages that are now irrelevant should disappear automatically.Current workaroundAfter deleting the object, manually re-validate that item to clear the message. It's just one click, but it's an unnecessary one — especially when cleaning up objects with multiple validation messages.
Currently, Thinkwise supports a Multiline control for plain text and an HTML control for formatted text. However, the HTML control requires HTML input, which is difficult to generate and maintain — especially in AI-driven workflows where markdown is the natural output format of language models.A native Markdown control would allow developers to store content as plain markdown text and render it as formatted output (headings, lists, bold/italic, code blocks) in the Universal GUI — read-only in grids and forms.Use cases:AI-generated content (user stories, descriptions, summaries) rendered directly in the application Documentation or knowledge base fields Any field where structured, readable text is needed without the complexity of HTMLProposed behavior:Read-only rendering of markdown in form and card list components In edit mode: plain text editor (like Multiline), or optionally a markdown editor with preview Available as a domain control, similar to how Multiline and HTML are currently offeredThe HTML control already proves there is demand for rich text rendering in Thinkwise applications. Markdown would be a lightweight, developer-friendly complement to it.
Currently the Upgrade script from the Software Factory will always fully rebuild tables. This can be quite an issue when you for example need to change all your trace columns default values from getdate to getutc date. In this case all tables within your DB will be rebuild. Causing a major load and issue when executing this upgrade.In my case I was unable to run this upgrade because of the LOG created during the upgrade. It was too large, over 100GB. My fix was a manually writing upgrade script, which did not rebuild the tables but simply used an alter table alter column statement.Result was great. Script ran in under 5 minutes. The rebuild script was running over 2 hours and still not finished.I think the Upgrade script should use alter table alter column when possible. Because it is much faster and has a significantly lower load on the server and log files.A few examples when an alter table alter column would be more than enough:Changed domain of a column Renamed a column Changed the default value of a column
Currently when you create a merge session the task to create a merge session will lock your Software Factory due to the fact that is waiting for result. I would this to run in the background, since the task sometimes takes 10-15 minutes. During the creating of the merge session, I would like to work within other branches. This can only be done, if you open a 2nd Software Factory. This not ideal. If the task would run in the background, you can keep working in the same Software Factory and when the merge session is created, check the result.
At this moment tooltips are not visible, can that be done? With an inline button, so that it also works on touch devices.
It’s not possible to give weekend days a background. That helps planners in their overview of there planning.It now can be done in CSS, but if you could add a simple option in the scheduler : Highlight weekend days eventual with the colornumberWhen this option is turned on, the css code is added to the css file when generating the application.Or is this too simple?
Hi everyone,I would like to propose a quality-of-life improvement: the ability to manually reorder menu items in Open Documents and Favorites using drag-and-drop.Why this helps: Better overview: Group related tabs and documents together based on your current task. Higher efficiency: Keep your most-used favorites at the very top for quick access. Cleaner workspace: Less time spent searching through static lists. It’s a small UX tweak that would make daily navigation in the Software Factory a lot smoother.Let me know what you think! Upvote if you agree.
Like the execute all at Functionality, add this option also to the deploy at Code overview
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.
In Release notes Thinkwise Platform 2026.1.11 | Thinkwise Community aggregations for groups were added. Unfortunately there is only an extended property to disable this for all subjects.Please make it possible to disable aggregations for groups on specific subjects.
When moving components around of a screen type it now is saved immediately. Please change it how it was in the older versions where an active “Save” was required to confirm your changes.When you now move a component and the result if the placement has an unintended result, your screen type is now ruined. Since the order of how you move component can be quite important to not completely mess up the already setup specification in width/height, a mistake can happen quite easily.
When a column is set to hidden and this column is not a PK, the column is often not supplied through Indicium. This is fine for most cases. However sometimes there are columns that should be hidden inside an application but should be available through Indicium. For example, an Interface ID column.Currently the only way to make this column available in Indicium is by setting the column to editable or read only and set it to hidden on grid, form and cardlist.I would like the option to enable a checkbox on role level that will make a hidden column authorized. This should result in the column being supplied through Indicium for this specific role.This way these kinds of columns can be made available to interfaces and remain hidden inside our application.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.