Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
A request I heard a lot from users over the years is to make it possible to select multiple rows in a lookup window and add them all at once. I don’t see a reason why it shouldn’t be possible if we accept the following limitations:The user must be adding a row (not editing). All fields (excepts for the lookup field) must be optional or filled with a default value. So no user interaction is required to add the row. Although maybe it could be possible to allow mandatory fields that are not filled with a default procedure if the user just enters it in the first row and the same value is used for all rows. So if the user wants to add multiple rows, he presses the ‘Add’ button, opens the lookup window and select multiple rows. The GUI should fill in the first row, save the row, automatically add the next row with the next selected value and continue this until all selected values are added. The default/layout procedure should be executed for each row. If one rows encounters a problem, for example one selected value is rejected in the default procedure, It should skip that row and continue with the next one. A same kind of summary popup with failed rows could be shown to the user as is done with the mass-update feature.
Can you please add an option to execute hotfixes from inside the hotfix screen, without the need of download and install a installation package.
I often have trouble finding the right icon. It would be great if I can describe the icon I want and have the Software Factory (using gen. AI) create an icon for me. Perhaps, as context, I should have a place where I can store the project guidelines for icon usage, for example colour usage, complexity, etc. This way, I get a more predictable outcome for the icon.In my mind the context given to the AI should be as follows: Object type (task, prefilter, table, etc.) Object name Object translation Object description (application specific) guidelines regarding icons Some sample icons coming from the current set Optional description of what I wantThe output should be a proposed icon (svg) that I can either: Accept and use Reply to and ask to generate a new icon
When the Global search field is shown as a button (without the text field), please make a visual indication when a search criteria is entered.
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
Hello all,We have a scenario where we want the user to navigate to a details tab, the user in this case is on a mobile device. While on a tablet, there are some options to make a detail tab appear on the side of the screen, this option is not doable for mobile phones. And some of our users are going to use mobile phones instead of tablets.We used a task link before, so the user can click on a task on a record, but this is not ideal. This is not the web and mobile way. As Nielsen and Norman's 10 usability heuristics put it: recognition rather than recall. On mobile and web applications (looking at apps like Outlook and Gmail) it is common to have a single click on a record. Just on the record, not on a task button integrated in the record.A user will recognise a single click on a card record to navigate to the details, rather than having to actively push an integrated button, link or a double click. This is all very Windows oriented and not quite how web and mobile apps are built. We find it to be inconsistent with web standards. So that is why I would like to request a single click option: as single click on a card record, like in Outlook or Gmail to get to a detail view of a said record via a task and (if necessary) process flow.Though I've seen merged ideas to the following idea: https://community.thinkwisesoftware.com/ideas/ability%2Dto%2Dshow%2Dtable%2Dtasks%2Don%2Dgrid%2Dline%2D518 This is not what we are looking for. This is still a new feature which is very Windows oriented. We don't want extra buttons in our records, we want the user to just click a record once and navigate to the desired details.This happens to fall nicely under the fourth Nielsen and Norman usability heuristic as well as the sixth:Consistency and StandardsUsers should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.Jakob's Law states that people spend most of their time using digital products other than yours. Users’ experiences with those other products set their expectations. Failing to maintain consistency may increase the users' cognitive load by forcing them to learn something new.Recognition Rather than RecallMinimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.Humans have limited short-term memories. Interfaces that promote recognition reduce the amount of cognitive effort required from users.At this point in time, we have quite a history of user actions on the internet, and the single click on a card record (like in Outlook or Gmail) is one of them. This would, instead of a new double click action, greatly increase usability of our software, especially for those that are not too well versed in computers and mobile devices.
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.
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?
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
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).
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.
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