Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
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.
Question (Jeroen van Herten):On a barcode scanner device we use the Universal GUI, we want to send feedback to the user using sounds without any text message. In the SF we can add a audio file to a message, but this only seems possible in combination with a popup/panel text message. Is there a way to only send audio? Note: An empty translation for the message still popups an empty box in the GUI which we don’t want. Reply (Mark Jongeling):I dont think that's possible at the moment. Throwing a message with audio without the message was not part of the implementation. But I can imagine this could be handy in some scenarios. Maybe the None (surpress) message location could be used for this, or a new one - Audio only. Feel free to create an idea for this Idea:The idea is to introduce Message location Audio only, as suggested by Mark Jongeling.As a result, the function of the existing Message locations remains unaffected.
When you double click on a pivot grid cell, you get a popup grid zoomed in on the aggregated rows.This popup grid cannot be controlled by the developer (except for hiding fields). We would like the possibility to setup this grid like every other grid, thus specify screentype, add tasks, add details, etc.Basically the popup grid should use the grid as specified in the subject (variant) that is used for the pivot grid.
In the windows gui you had the option to show the application without any translations. This functionality is missing from universal. For debugging purposes I would very much like this option to return. When I investigate a problem on an environment I don’t know I have to use the translated object, translate this to the database object. Then revert this to get the menu objects I need. I know application insights is a thing. But that doesn’t always work and is still not as fast as just showing the application without translation used to be.
Description:Enable developers to define a standard task bar at the top of the Universal GUI, similar to the task bar in the Windows application.Rationale:A consistent top-level task bar improves navigation and user experience. It provides quick access to frequently used actions, enhances branding, and aligns Universal more closely with the Windows GUI experience.Additionally, it helps prevent redundancy such as having the same buttons repeated across the screen by centralizing common actions in a single, reusable interface element. -example of duplicate buttons across screen views-old windows lint Suggested Implementation:Allow developers to configure task bar contents in the Software Factory. Support buttons, icons, dropdowns, and user-specific actions. Make it optionally persistent across screens or context-sensitive. Include styling options to match application themes. The lint reacts to the selected detail view on the screen
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
Description:Introduce the ability for developers to define custom font sizes for components within the Universal GUI. This should be configurable at design-time, allowing consistent styling across forms, grids, and other interface elements.Rationale:Currently, font sizes are fixed and not adjustable per component. Developers need more control to ensure visual hierarchy, accessibility, and consistency. This is especially important for applications with complex layouts. Since we want tot avoid using custom css as much as possible it would be great if there was a way to change this through the SF.Suggested Implementation:Add font size properties to relevant GUI components in the Software Factory. Allow configuration per screen element (e.g., form fields, grid headers, labels). Support standard units (px, em, rem) or predefined size categories (e.g., Small, Medium, Large). Ensure compatibility with responsive design principles.
Can you please add a property in the domain settings to set a specific collation to particular domains.This because some kind of values, like MS Graph ID’s, require this.
We would like support for HMAC authentication in Web connections.We want to connect to webhooks that have limited authentication types, HMAC is the most secure option it does support.
During development, the "Refresh Model" task may be called hundreds of times per day.It might be an idea to move the task to the header bar or assign a Shortkey to the task.And at the same time ignore all warnings, because they do not matter during development. This will definitely save a lot of time during development.
When refreshing a model in the windows gui. all active tabs remain open after reloading the application. Doing this in universal only the active tab remains intact. All others are closed. When developing or trouble shooting something that involves multiple screens it can become annoying really quick to have to reopen the screens on each model refresh. Can we keep the active (still existing) tabs open on a model refresh in universal?
Model insights is very difficult to use with the introduction of the hyperlinks in the form. Now instead of getting information on the field you open the hyperlink instead. This makes debugging a lot more tricky then it needs to be. I would propose to deactivate the hyperlink functionality when using the model insights to make it more user friendly. Or alternatively only make the actual word a hyperlink like how it functions in the grid.
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 feature would be ever better if a user could right-click on the link to choose how to open the lookup (similar to a hyperlink on a website).-Open as popup-Open as new document-Open as new browser tab-Open as new browser windowBonus points if the default way of opening (left-click) is configurable for each lookup in the SF.
Sometimes there are things that are linked to a variety of subjects, like relationship that are linked to objects or object_parts or contracts. Now I have a subject in which I want to use a relationship, but sometimes I would like to add a relationship that is linked to an object and sometimes I want to add a relationship that is linked to a contract. I thought I might use a variant that uses a lookup for relationship for objects in one instant and a lookup for relationships for contracts in the other instant. However the lookup of a variant cannot change and is always the same as was specified in the default. I would like to be able to assign a different lookup table to a variant.
Using UP, it is already possible to create and save your own prefilters, by entering values for the available columns in the table. This always leads to an and-based prefilter, which has limited options. I would like to be able to make my prefilters by writing a query or by saving my filter expressions. This way you can also make your own or-based prefilters, use subqueries or joins, etc.
It's difficult to delete a table or task if it turns out to be part of a process flow. You do get a notification, but it's not easy to determine which process flow(s) it's in. We would like to see an overview of the relevant process flow(s) in addition to the warning.
IAM is available in a few languages, but users of IAM need to assign roles to user groups based on the name of the role and the description. With internationalisation in mind and not knowing what language the IAM user understands, we need to be able to provide the names and descriptions of the roles in each language that IAM is available in. Not just the language the application is made in.
Goal:I would like to be able to change the primary action status of tasks via the context procedure.Use case:An ordering process with 3 statuses: new, ready to send, and sent.I want to apply the call-to-action color to the task that triggers the correct next status in the process.By default, I've configured the “new order” task as call-to-action.However, when there is an order that is ready to be sent, I'd like to make the “send” task the call-to-action instead. Meanwhile, the “new order” task should still remain available to users as a regular task.Workaround:Currently, we can only achieve this by making duplicates of the tasks (1 regular and 1 call-to-action per status) and by using the context procedure to hide all the ones we don’t need per status. For 2-3 statuses this is okay, but for a process with a lot of statuses this quickly becomes very cluttered, both in the tasks and the context procedure. Solution:In the context procedure, add a new type for tasks.E.g.: @[task_name]_type -- tasks. 0 = enabled, 1 = disabled, 2 = hidden, 3 = primary action. (or use nr. 1 to follow the logical order, in that case also make an enrichment to change all existing context procedures)
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.
Our application is running on a database which is in UTC (Azure SQL), this does come with a unique set of challenges as our business operates in CEST.IAM is giving one of these challenges with it's scheduler, there are a few schedules that should be ran every day at a specific time. This time however is in CEST and the scheduler it's time is in UTC, in practise this means we have to change the schedule twice per year. Please add the possibility to select the timezone for which the schedule is set in. This way IAM can handle the time changes due to summer/wintertime and the actual running time is always the same from a user perspective.
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