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.

Hi, I'm not sure if this is possible but I will share something that I just experienced. I have a query that creates/updates data in several entities. This query has 200 lines which is heavy enough. I need 2/3 validations before doing this heavy CRUD, I would like to do that inside the Advanced SQL node and be able to output the error code and error message. As of today, the only error that comes out of a query is "Error executing query" which doesn't allow me to handle the error properly. To accomplish those validations, I need to have more aggregates or even SQL nodes outside the heavy create/update which will increase even further the complexity of the action.

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.

When on the ODC Portal, the user can view and configure the apps that are in each Stage, however, the navigation through these can be enhanced. Currently, when the user accesses the Apps menu, and then opens an Application, the Stage is always set as Development . Even if the users change the Stage to QA for instance, when navigating back to the Apps list, and opening another App, the Stage is reset to Development . This is annoying because if the user is performing a considerable amount of configurations, he/she is always obliged to change the Stage for each App he/she wants to configure. What do you think of keeping the value of the Stage in a client variable? This way it would facilitate a lot of the scenario described above as it would be a lot less clicks to reach the same goal.

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

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.

It would be nice if the platform could expose the underlying stack(.net, js, ...any?) bitwise operators at the Built-In functions, maybe a "Bitwise" folder with AND, OR, Complement, Left Shift and Right Shift.There are several applications for this when masking, dealing with multiple checkboxes/radios, datapoints, conversions, algorithms, and even external connectors to SBCs/Microcontrollers.It seems a bit overkill to have a forge component or adding an extension/block for it.

At this moment, the "By" of listSort is not dynamic, which means it will not allow a variable that does not have the same name as one of the columns in the list. This will result in having something like: 1st option or 2nd option It would be interesting to have something like this: Since the "SortBy" would already bring the name of the column, it would be something straightforward.

By Default fill in the Description Section of the Aggregate and Timers when a new aggregate or timer or any variable is created to avoid Architecture Dashboard Issues.The user can then change it to any values he wants. This will avoid issues on the Architecture Dashboard which in turn will increase the development speed.

Cyclic References need to be True Change warnings.J.Ja