Recently active topics

In the Web GUI it was possible to use “Select all” and when activating a task it would ask if you wanted the records on the page or all records of all pages. Please add this also in the Universal and in addition make it work with the Multi Select XML parameter, as this popup did not seem to happen in that case.

Hello!I created this idea as result of this post: Basically, what we suggest is that there should be an option to specify the lookup control for grid filters, we received feedback from users about this and since that can be changed for form/tasks, will be nice to have it also in here.Regarding performance mentioned in the post, one solution can be to have the sort defined and then pick top 100 for example and if you don't have what you want there to still be able to type and search it.  

A use case that happens ins many cases is where you have the grid with a detail tab with the form and other elements. For the user It's quite cumbersome to be going back and forth every time he wants to see the details of a couple of items in a row. I really miss the previous and next navigation buttons in the detail, where you can jump easily to the next or previous item in the context without the need to go back. 

Based on the question I posted yesterday, I asked if its possible to have an optionfor a field to be responsive in height for Universal GUI. This can be used for fields that are meant for paragraphs of strings, like HTML and multilines since we only have in my knowledge to set fix height in SF->Subjects.Responsive field height for example will try to extend its height based on the remainingspace if there are available below it. This is very useful for applications that can be used for mobile view and web view Question:https://community.thinkwisesoftware.com/questions-conversations-78/is-it-possible-to-have-responsive-field-height-in-universal-gui-2785

When you make an existing column in a table mandatory (and no default value is set), you get a very helpful validation warning you to setup the data migration for this column.When you create a unique index on an existing column (or set of columns), no validation will be shown.It would be nice to have a warning in the validations list to show the developer that this could lead to issues.

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.  

Just like with tasks, I would like to create and use dummy reports. The reason for this is so the icons in the application are better ordered. Tasks are with other tasks and reports with other reports.Left Tasks - Right ReportsThe reason we need a dummy report is to start a process flow. The process flow then activates a task that will insert a row in a sort of Queue table. This queue table will limit the selection of rows that DevExpress will use to make it's report; thus making the process a lot faster.So this task need to be run before opening the report. But the task cannot be the starting point for the process flow and therefor we need to use a dummy report.

In the Debug Center both the error log and the database event log both have clear button. But the process flow monitor does not. Sometimes you want to clear this screen please also add a clear button. 

In edit mode you can add input constraints with regex that gives user feedback in the form. However, in the grid it only surrounds the field itself with a red line. It does not give any feedback to the user. It would be nice if the user knows what is wrong with the input value when editing in the grid.This field in the grid has an input constraint and only gets a red line 

In a current customer project, the customer indicated an issue with how numeric and integer fields handle input length restrictions.At the moment, when a numeric or integer field is configured with a maximum of, for example, 6 digits, users are still able to enter more than 6 digits. This results in a validation error message such as: “Artikel nr heeft teveel cijfers”However, the customer expects the behavior to be consistent with varchar fields. For varchar fields (for example varchar(6)) users are prevented from entering more than 6 characters in the first place.Requested improvement:Align the behavior of numeric and integer fields with varchar fields, users are prevented from entering more digits than the configured maximum length, instead of receiving an error message afterward.

SummaryAllow Thinkwise customers to share AI-enrichments they've created in their own Software Factory to a central, curated repository managed by Thinkwise — so that the entire customer community can discover, import, and benefit from enrichments written by others.The Problem TodayEach Thinkwise development-team develops AI-enrichments independently in their own Software Factory. There is no mechanism to share these enrichments with the broader Thinkwise community, which means:Customers reinvent the wheel building similar or identical enrichments. Valuable knowledge and innovation stays locked inside individual tenants. Smaller teams with fewer resources benefit less from AI capabilities compared to larger customers who invest more in development.The Proposed SolutionIntroduce a Shared AI-Enrichment Hub within the Software Factory, with the following flow:Create locally — A customer builds an AI-enrichment in their own Software Factory as they do today. Opt-in to share — The customer

Context  To create different grid layouts (i.e. active columns, sort order, fixed columns, etc) for users, we now have to rely on developers (i.e. design-time) to create Variants. Variants are a good way to also control many other things in a screen, but oftentimes users only want a different grid layout (mostly when they change a prefilter) while the rest of the screen must remain the same.  An example of this is when a user switches between working with open sales-orderlines or invoiced sales-orderlines:  When working with open sales-orderlines, the invoice-ID-column is not relevant but showing the available stock columns is.   When working with invoiced sales-orderliness, the invoice-ID-column is relevant but the available stock column is not.   It is currently also not possible to not have only a selection of all possible columns activated when a user opens a screen for the first time (now default behavior is all columns are active and this cannot be controlled).   Feature request