Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Hi All,The scenario is simple.I have a User which logged in the application in Universal GUI 2022.10 and since then has not accessed the app. We upgrade the GUI to 2023.1.12 in the mean time. They then try to access it now and get the top popup for New version is out etc.. but they ignore it.Not having latest GUI version will be mising optimizations, improvements, and functionality supported by latest version right ?We need to force the GUI update on the Users, so that when a new GUI version is out they automatically get it when loging in. Everyone please vote :) Thanks
I would like to be able to launch a task from an unsaved form.The task starts with the parameters entered by the user. The task should be able to adjust the fields.Business case;The user is entering data, I want to give the user a button which does assumptions based on the entered data and autofill fields with the most likely data. As the default procedure can not call into another system the user has to press a button to do this, but it should be before save.We have 2 tools in place;1) If the user can fill in a complete unidata code, we can look up the product properties on our unicat website.2) If we have a “crappy” product description from the user we can have chat GPT improve it.To build those 2 options in the user interface we need an option to start the task from an unsaved record.How it should work;The user is entering data and can press a “fix this” button, the workflow presents a number of possible fixes. When the suggestions are right the user clicks ok, and the open form is updated with the suggestions. When the suggestions are bad, the user clicks cancel and nothing changes.
I would like to see that when you click on one of the line number rows in code search, the template code on the right would jump to (and possibly highlight) the row:This would save a lot of time scrolling and looking for the line numbers to check code 😃
Can the date selector be modified so that it can also display the week numbers according to the ISO standard?The week numbers currently displayed do not correspond to the week numbers according to European standard. This is very confusing and can even lead to major misunderstandings.The extended property 'UseISOweekgroupintervals' also makes no difference. See also ticket: 2370S in TCPNB. The behavior of the data selector, with regard to week numbers, should not depend on the regional settings of the server.
It doesn’t make sense to set filters and pre-filters in the context procedure, as it could be the context of a list and navigating through the items should not change them.But if we redefine what the context procedure does, and state that it doesn’t only allow to modify the context but also to see the context, it makes sense and it would make it possible to solve something that seems like an unsolvable Thinkwise puzzle at the moment.I want the report button to be filtered by the users filters, and I want more things, …, at this moment it is possible to set the filters with a workflow, but I can’t get them. The context procedure would be the logical place to retrieve the last selected value.
When setting up a form in the SF it is possible to set a ‘Field on next tabpage’. The universal GUI translates tabpage to scrollable sections, which is great to structure forms with many fields while maintaining the positions recognisable for a user when scaling the GUI into a different size. However each tabpage currently scales into it's own amount of columns, making the layout really messy and unprofessional.Here is an example with the ‘No. of columns in form’ set to 3. The default field width is set to 300 and the subject field with is set to 225 for all fields (so there is some white space between columns to keep it less crowded). The problem in this example is that ‘Specification’ and ‘References’ scale into 2 columns instead of 3 because of the amount of visible fields in those sections. The fields in these sections also become wider this way.The exception in this example is ‘Remarks’. It should still be possible to set a specific field to use the full width of the form. But this should be the same width as all columns combined (including the white space between them). So what we would like to achieve with this idea is that all tabpages of a form always scale into the same amount columns, unless there has been made an exception for a specific field to use the whole width of the form.
While doing the deployment it happens to have unit tests/smoke tests that are failing.If they are failing and you did not do another deployment you will not see in the validations that they are failing, the same goes if you fix them, without running again the deployment you are not aware in validations that they are fixed.I think it will be useful in this case, but also in others, if you fix something that is in validations, to be updated also there.
At this moment it is possible to deactivate a control procedure which gives the possibility to deactivate them first see if they are really not needed and delete them later or to save them as a reference as they are not used at the moment but might be in the future.I think that the person who created this has a great and brilliant insight but …If something is possible for one thing … why wouldn’t it generally be possible for everything?My idea is that someone should take a big spin through the application and generalize this.The reason that I come up with this is that a consultant put work in setting up the flows for microsoft graph integration. I decided that we should not use it for the functionality we are building now, but I don’t want to throw away the code workflows and tables, etc.
This idea came about due to having a column with a dropdown control (records selectable though a reference to another table/view), but wanting to always have the records on display and not just expand the dropwdown on click.Thus, the issue at hand is to always have the records visible on screen for that column.We would be interested in a solution that displays the records as separate selectable checkboxes (see image below). The checkboxes can be selected as a domain control type, but they do not produce this result. It is possible, however, that we might be missing something. The context behind this idea is a very specific one. We have made this with a view, however, for our purposes, it gets to have an inconsistent feel due to other functionalities in our table. Having them be displayed with checkboxes like above, instead of a dropdown, would be a perfect solution. We would also be open to a solution that could force the dropdown to always be expanded, thus removing the need for an extra click.
When Im running a creation script that fails I’d like to know the line number along the error message. This will give me a indication where the error is located.
As it is now double clicking on a detail tab in universal does something that, is as I see it confusing. One of the things is that I suddenly have another page, and that I don’t have an option to go back to where I was. Accidentally double clicking a tab results in being lost. There are also some bugs I noticed in the software factory; if you double click on a tab with an active search filter the zoom window doesn’t show the search filter but does apply it. Web and universal are different then a windows interface and I don’t think that this functionality will ever work the same in universal as it does in windows. I would like to have the option to create a workflow which opens an item after double clicking in a big almost screen size popup window with a close button in the upper right corner. ----This might already be possibleThis might already be possible with a workaround I did not try; create a screen type without detail tabs, create a detail tab, open the detail tab with a workflow starting with double click, add a big back action button in the upper right corner, add the back route to the workflow.The problem with this solution is that it will create a big spider web workflow, if you want all entities to generally be clickable and generally show a popup window, and you have for example 10 different entities which relate to each other, …, I don’t know if someone can think of a smarter way but I end up with 10 forward tasks with each 10 table tasks, 10 table variants for each entity and 10 backward tasks with table tasks for each entity, and a workflow which can be started by 100 different table tasks. ---The big challenge behind this idea is to make this possible with less “low code”. My first idea is that you could add a checkbox “Zoom on doubleclick” (in the SF) for all subjects / variants for each “zoom” detail. That way my example above reduces to one detail mapping in the forward relationships, but Universal has to remember the back route and show it in the interface.The result should be that it is possible to generalize opening popups with detail information.(It is also possible not to reuse the zoom screen type and add a popup screen type to all the entities, it is more work but might be cleaner).
With the help of breakpoints we are now able to design screens that work well on almost any screen size.However, some screens are specifically designed for the desktop and it makes no sense to have them available on smaller devices, such as those of a mobile phone or tablet.I wish there was a way to indicate this in the model. By means of a special breakpoint, or menu item setting, which ensures that menu items for these screens are only available for screen sizes within a certain range. Typical examples are schedulers or plan boards.
When importing a file using the standard import functionality it is possible to use default logic on the imported records (by using @import_mode). It is at this moment not possible to identify the importsession. Therefore it is not possible to distinguish currently imported records from previously imported records. I would like to see a unique identifier to distinguish the different import sessions from each other, available within the default template.
The width of checkbox fields should always be fixed.We believe, making the width variable and depend on the total available width makes no sense. Unwanted behavior in a FormList scenario:
I think that it would be good if we would be able to specify database timeouts on both a global and a more detailed view / subject / task level.I posted this as a question before; Sometimes things can end up running so long in the background that the user won’t wait for them anymore, I think that it would be good if we would be able to set a general timeout for all views, and queries. Next to this it would be good to set a larger timeout for some tasks and specific views, as some things could take longer than “normal”.
It would be helpfull if I could decide the task variant my process flow uses as a start object when using a table task. It is possible for the ‘start task’ but not for the ‘start table task’ process action. I want to use this to implement different task behaviour per table variant:
Currently there is no way to assure that a role (or user group) should not co-exist (within a user or user group) with another role.For example one user should not be able to create a credit invoice and pay the same credit invoice. In some cases you want this to be done by separate people within the business.It would be good to be able to create a matrix of roles that should not be assigned to the same user or user group.When a user tries to assign an illegal combination of roles to a group or a user (due to a combination of groups) IAM should not let you and give a warning.
In many ways the new database event log is a big improvement but I am encountering that the new overview isn't showing the request parameters, thus making finding the request I'm looking for more hassle than needed.Also there is an request ID in the database event log but this ID isn't available in the HTTP response, so relating a HTTP response directly to an event log isn’t possible (only assumptions based on time etc) It would be very nice to be able to always show or at the very least make it possible to enable showing the request parameters in the new log and to add the RequestID to the HTTP response headers thus making the relation 100% clear (and searchable!) Example:Event logNetwork Relation between these requests is only possible based on assumptions and this is the simplest example I can create, most situations are a lot more complicated.
The text in the dialog box of tasks is too technical for the user. Do you want to execute task Undo approved declaration should be “Do you want to undo approved declaration.” Execute task does not add anything for a typical user.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.