Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Goals of this feature request:The sidebar navigation menu hamburger icon and screen name can be positioned more logically and consistently across all screen sizes (mobile / desktop). On expanding the menu from a collapsed state, the user currently no longer sees the screen name. Make this visible. Introduce a fully collapsed menu state for maximum use of horizontal screen real estate. The current sidebar states are as following: We suggest to make the hamburger switcher stick to the left of the topbar. And then let the navigation sidebar work from below the topbar (it currently overlays it). Also introduce the possibility for a three-state navigation sidebar (instead of two-state) by clicking the hamburger icon (sequence 1 > 2 > 3 > back to 1): Fully expanded state Partially collapsed state Fully collapsed state (maximum horizontal screen real estate In a sidebar collapsed state, the menu should expand when the user hovers over the hamburger icon (this is something currently missing as well). This behavior is required to expand the sidebar from a fully collapsed state, while still be able to collapse it again when the user leaves the hover-over. This feature request also coincides with another feature that is already underway, and that is being able to use ALT + M shortcut to automatically set focus to the search field of the navigation sidebar. For power users (which most users are using Thinkwise systems) the fully collapsed sidebar state in combination with ALT + M to quickly find the menu-item they know (and return to new screen with collapsed menu), provides them with maximum screen real estate to work on at all time while still attaining a fast navigation flow. The end result is also a consistent hamburger menu positioning and sidebar menu behavior across all device types.
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.
At the moment, it is possible in a cube view to define a dimension and a value that both refer to the same field in the underlying table. This is not logical, and a cube in which a value field and a dimension field both reference the same table field results in errors when opening the cube in the Universal GUI.My suggestion would be to implement a check constraint in the cube_field table of the model database to prevent this.
The mass-update button is a bit hidden behind the three-dot button. Could the Edit button react based on how many rows are selected? So if you have one row selected and press the Edit button you get the current behaviour, but if you have multiple rows selected and press the Edit button it opens the mass-update popup.
Currently, we allow numeric badges on tab pages and menu items. This works well for counts (e.g. number of records, open tasks).However, there are many situations where a number is not the right signal, but the user should still be visually alerted.The limitation of numeric badgesNumeric badges implicitly communicate:Quantity Work to be done BacklogBut sometimes the intent is different:“Something needs attention” “There is uncertainty or missing information” “This section contains an exception or warning”Using a number in those cases:Adds unnecessary cognitive load (“what does this number mean?”) Can be misleading (“do I really have 1 thing to do?”) Trains users to ignore badges if they are often not actionableProposal: Support symbolic / icon‑based indicatorsAllow tab pages and menu items to display non‑numeric indicators, such as:⚠️ Exclamation mark (attention required) ❓ Question mark (incomplete / unclear data) ⛔ Error icon (invalid or blocking state) ✅ Check icon (explicitly OK / completed) ● Dot indicator (something changed)These indicators would be data‑driven, just like numeric badges today.Why this is valuable1. Better alignment with user intentIcons communicate state, not quantity.This matches many real‑world business scenarios better than numbers.Examples:A tab contains inconsistent data → ⚠️ Required fields are missing → ❓ Validation failed → ⛔ Approval completed → ✅2. Faster visual scanningUsers don’t read numbers — they scan for patterns.Icons:Are recognized instantly Reduce interpretation time Draw attention without demanding actionThis is especially effective in:Complex screens with many tabs Role‑based applications where users need guidance Review or exception‑driven workflows3. Prevents notification fatigueNumeric badges can feel like “todo counters”. When everything shows a number, users start ignoring them.Symbolic indicators:Feel lighter Communicate importance, not volume Are less stressful and more selective4. Improves guidance without extra UIThis approach:Avoids adding extra columns, banners or messages Keeps the UI clean Uses existing UI real estate more effectivelyIt’s a low‑visual‑noise, high‑signal improvement.5. Backward compatible and complementaryThis would not replace numeric badges, but complement them:Numbers → “how many” Icons → “what kind of state”Developers choose the most appropriate signal per use case.Example use cases Customer screen “Details” tab → ✅ “Contracts” tab → ⚠️ (expired contract) “Documents” tab → ❓ (missing upload) Workflow‑driven application Menu item “Review” → ● (new activity) Menu item “Errors” → ⛔ (blocking issues) Master‑detail screens Child tab highlights issues without forcing users to open each tab Optional implementation direction (high‑level)Allow badge type to be: Numeric Domain with elements and Icon Icon visibility driven by badge logic / domain value Optional tooltip to explain the meaning
Universal UI allows you to mark screens as favourites and automatically open them on login, which is great.However, the order in which favourite screens open cannot be changed.They always open in a fixed sequence.Why this mattersOften, I want:Context screens (overview, dashboards) to open first My main working screen to open last, so it has focus and I can start working immediatelyRight now, I need to manually switch tabs every time I log in.ProposalAllow users to reorder their favourite screens, so the login sequence matches their personal workflow.This would be a small UX improvement with a noticeable productivity benefit, especially for users who log in frequently and work from a primary screen most of the day.
Upon opening a new Document in the Universal GUI the first value in the top left (at least for Western writing) Screen Component should be activated. This especially goes for the Grid component, where it seems as if the first Row is selected. In below example it took me 44 tabs to get to the first column value of the seemingly selected Row. Could the Universal GUI be a bit smarter here?
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.
In the Windows GUI a developer could choose to disable translations of domains and fields. This comes in as very handy when one wants to see which field is shown in, for example, a form. In my case, depending on what box is checked, a field called supplier_no is shown or homedealer_supplier_no: Switching on / off for translations in Windows GUI: I have not yet found the same functionality in the Universal GUI. Perhaps something to support in the future?
it would be great if Universal GUI/Indicium can determine if the user is on the local network or somewhere ‘outside’.In case we can determine the inside or outside location, it should be possible to configure the “login verification” at the user (or maybe application ?) per location.E.g.LAN login verification: “Password” Non-LAN login verification: “Password and TOTP token”This will make it possible to setup MFA for external usage, and avoid the additional factor in case working on the LAN.
Can you please add an option to execute hotfixes from inside the hotfix screen, without the need of download and install a installation package.
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
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
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.
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).
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