Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
when adding a process step in a process flow from decision to the next action, this is added as always even if i change it to (un)successful. It adds value if it´s possible to add a qualification like (un)successful or maybe add a separate description.
With GUI version 2025.2.13.0.0 a new behavior for lookup fields in the grid was introduced Universal GUI version 2025.2.13 | Thinkwise CommunityThe behavior in the grid is unexpectedIn grids, when a row is active or hovered, the lookup text is styled with the Accent color. When hovering over the lookup cell, an underline appears to indicate interactivity.Even though there might be situations that this can be useful, by default this is a behavior we did not have and also do not need. We would like to see that this grid behavior can be activated/deactivated. The default should be deactivated - since this was non existing before.
With the new custom toolbar we can assign screen areas for tasks or prefilters, and also define default display type. But what if for example import or export is important for a specific subject. The only option is to create a specific screen type for that subject, so a standard component can be assigned a different display typeIn our specific case, we have a working list where we start with import of a list. So, we would like to add the import component as Icon + text on a specific subject. Would be nice to have this option at permissions, to define screen area & display type
It is currently possible to link a base model to a work model. But if you want to change something, you will have to do it in the base model. This makes it impossible to integrate it with other objects of your model.I would like to have the option to import a full base model into a work model instead of just linking it. Basically the same result as using the ‘Unlink generated object’ on all objects of the base model.This would make it easier to integrate Thinkstore projects into our own projects.
Idea created after response in ticket: In Azure OpenAI it is possible for a “Content filter” to trigger and results in a 400 status code. https://go.microsoft.com/fwlink/?linkid=2198766Instead of having the LLM process action in the flow give a -1 (unknown) and no other information, give it a different code or additionally some info that is was the “Content filter” that triggered. This way the error handling can be more user friendly in this situation.
We have a few custom code groups currently we are unable to assign these to Program Objects via the user interface so we are forced to use the SQL assignment to assign them. The SQL assignments are not always ideal for various reasons so I'd like to propose the following: Being able to create a mapping from a custom code group to multiple build in code groups and use this to show the correct Program Objects in the assignment.
As I'm advancing step by step with the process flow, I unfortunately increase the amounts of problems I create for myself. Something theat happens often, is that I create an infinite loop in the process flow. Ofcourse, one should be carefull, of course one should always take measures to prevent, of course a lot should be done to prevent this. But fact is that a small mistake may create an infinite loop in the process flow, and form that momento on, its just impossible to stop the loop. The only way is to restart stuff, to which I do not have any access. And if I'm playing around in the evening, often our servers are running red during the night untill someone can restart. So, I'm askin, almost urging to please make something that kills the process flow, so a developer can also correct himself without going through the humiliation of confessing a s***d up once again. ;-)
I'm already becoming a fan of the collapsible sections in a form. Now I was looking at a comparison screen we have between ERP data and read data from a document. Would be pretty great if based on detected differences we could auto-collapse a segment.
We would like to have the ability to use Push Notifications on Demand to send custom messages to our users. Currently the only notification that you get from the Universal GUI is during a system Upgrade to a new version, or once asking you to install the app on your device. The Idea is to have a built in way for push notifications on demand to users fromwithin the build application IAM Both the aboveSending a notification to users for critical items as per the developed application demands.Optional if possible to be able to select the delivery medium from:SMS iOS, Android, and web push Notifications
We have some tables with start and end dates per row. When we do an export we see that all dates are no longer in the format that we used in the app. In Universal we use dd-MM-yyyy and the downloaded file uses MM-dd-yyyy.We would like the export function to follow the date representation that the user within the application has.
The Software Factory generates different translation objects for columns and report/task parameters. Often I would like these to have the same translation. Currently I have to manually copy the translation from my column into the task or report parameter.It would be great if you would have an option in the translation screen to copy the translation from a different translation object type. For example, have to option to copy the column translation for my task parameter. Obviously, the parameter name and column name should match for this feature to work.Column employee_id has translation Employee. Task parameter employee_id has no translation. This new task will copy the translation from column employee_id to task parameter employee_id.
It is possible to create a custom constraint on a table, so you can add specific checks without having to create a trigger. The message can be created with a dynamic model procedure like this:insert into #msg( msg_id ,msg_description ,msg_location_id ,severity ,msg_error_code ,msg_regular_expression )select 'err_check_constraint_' + tcc.check_constraint_id as msg_id , 'Translation for check constraint error: ' + tcc.check_constraint_id as msg_description , 'popup' as msg_location_id , 0 as severity --error , 547 as msg_error_code --error code when check constraint fails , '.*"' + tcc.check_constraint_id + '".*' as msg_regular_expression --regex that will find the specific constraint from tab_check_constraint tcc where tcc.model_id = @model_id and tcc.branch_id = @branch_id and tcc.generated_by_control_proc_id is null --only manual Then, you have to search in generated translation objects, or the message, with the name of the constraint in it. It would be very helpful, when you can translate the message as a detail of the constraint, just like you can do this on for example a column. The trick now, that it is not a translation, but a message with a translation. The idea is, that this message object is automatically generated, and that it is available on the constraint as a detail, so you can directly translate it. You need this, don't you?
On a few occasions we use the history table to calculatie timings and would like to add an index to the history table for improved performance.
Currently sequences are not allowed to be configured as default constraint on a table column. However this would make dev life easier if we could do an insert on a table without having to fetch the next sequence value explicitly. It would work similarly to an identity seed, however you could use the sequence on multiple tables to have a shared unique value, this is a powerful concept.Currently you can build a work-around with tags and dynamic code, but it would be better if it were integrated into de software factory so that it is visibile in the right place and avoids complexity and confusion for new developers.
The WMS application we are developing integrates extensively with external systems, such as picking solutions and ERP platforms.Communication between these systems is handled through XML messaging. Occasionally, a message may fail.For example, when an incorrect value is provided, such as sending a string where an integer is expected.Whenever an error occurs, whether due to syntax or processing issues, the XML message is stored in a designated failed folder. At the same time, a record is created in the application’s interface_error table. This record contains both the XML body and the corresponding error message, enabling users to review the failed message. From there, they can choose to resend it to the target system or take alternative corrective actions.To improve readability and usability, we would like to display the XML content using pretty print formatting in the multiline form field.So it looks like this:In stead of this:
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