Create a grid component that has advanced features like dragable columns, native grid editable fields, filter options, resizable columns, better sorting.  The Kendo UI grids are a good example.https://demos.telerik.com/kendo-ui/grid/index

In O11 , when you copy logic, screens, or any other elements from one ( source ) module and paste them into another ( destination ) module, any external references used by the copied elements of the source module are automatically added to the destination module. This is quite helpful sometimes, especially when you are trying to copy screens/logic from one application to another (I had to do this a bunch of times in the past, for various reasons). However, in ODC , this is not the case. Once some elements (referencing some dependencies) are copied from one module to another, none of the references are automatically added (unlike in O11 ). This results in hundreds of errors sometimes, which could be reduced to just a few if automatic dependency referencing worked like in O11 . It would be great if this automatic dependency referencing is added to ODC as well, unless there's a valid reason for excluding this feature in ODC . Thanks in advance, looking forward to hearing about others' experiences and feedback :)

Dropdown Search widget puts a margin at the end of the selected value, in order to create a buffer between the value and the action in the end. However, in pages with right-to-left direction, the margin is not reversed, it remains the same. Here is an example of LTR & RTL pages: English Arabic

Hello, I created this topic because I have noticed a major problem with interpreting information to take the certification exam, especially when taking it in person at an application center. In Brazil specifically, the use of digital documents (virtual documents via cell phone) is officially permitted (by the government). The problem is that nowhere does it specify the use of physical documents (paper or card), and people are prevented from taking the certification exam for not carrying the physical document. According to Prometric, they are very strict and I do not have the power to communicate with them for this small adjustment, therefore, OutSystems, as their client, could request this adjustment in the mandatory documentation information and even change the notice on the website, on the certification page. Recently, there was a case in which the candidate called the police and caused a great deal of inconvenience for not carrying the physical document.

When recovering deleted code or working with another person in the same app, during merge and publish it would be very helpful to have an option to 'Select All' for the versions we want, instead of selecting them one by one.

When we have the need to invoke the same entity twice in advanced queries we have the absolute need to put an alias in one of them, to distinguish them. The thing is that service studio puts a warning to it if you use Alias.* ... Perhaps one could assign an alias to the output structure?

As I said, back in 2017 , that idea had just been half-implemented, so I think it would be very helpful if the SQL editor had matching parentheses highlighting as well.

Allow dropping one assign element on top of another. This would copy all assignment variables from the first assign to the destination and delete the first assign from the flow.Allow also to select multiple variables of an assign and drag-drop on another assignment element. This would move those variable to the other assignment. Allow to do this with CTRL+Drag, which instead of moving would copy the variables assignment.

Hello everyone, My team is in a project with now bordering 150 applications in DEV environment. We have a domain driven architecture and can divide the applications using those domains. We would like to be able to setup a solution/cluster of applications and deploy them between environment instead of having to pick individually from a 150 application pool on every deploy. So the idea is to be able to create a deploy cluster with 20 applications and then in lifetime select to deploy that cluster. Best regards, Daniel Gonçalves

Add to Entities the Default Value Behavior property similar to what already exists to external databases ( Entity Properties - OutSystems ) so that the default values can be stored as null values in the database when needed.This will prevent developer the need to create their own CRUD SQL queries and use the actions provided by OutSystems when they want to persist NULL value in the database.