At the moment the Deployment of Applications in ODC is done one by one. What could be improved here would be the feature to prepare and place running Deployments of Several Apps in one go.

It would be tremendously more eficient for us, if there we can delete the variable and the assign value with one single button. Instead delete 1st the variable and the the value.If you need to delete 5 variable and the corresponding values instead of:   click variable   select all   delete   click value   select all   delete   repeat more 4 times the set of action mention.with the button should be like delete 5 times and done, we dont need to do 30 actions to delete 5 variables.thank you

When I compare/merge an espace with another version, then I also get differences like: - Position of elements have changed - Translation Behavior has changed In most cases I'm not interested in those changes, so it would be nice if I can turn those off. In this way it's easier to see what's really changed in the eSpace.

 Nullish coalescing operator (??) is a logical operator that returns its right-hand side operand when its left-hand side operand is null or undefined, and otherwise returns its left-hand side operand. This is widely supported and a great productive boost for those of us writing javascript in OutSystems. The problem with using this in OutSystems is twofold: the javascript editor considers it as a syntax error it is not possible to publish a solution that includes a module that has a javascript using this operator Could this be improved? Thanks, Tiago

It would really save time if there was the ability to navigate from a widget that uses an action as an event handler straight to that action rather than having to look at the widget for the name and then find that action manually on the screen. Some sort of button or double click functionality to be able to click on that action in the widget and then that takes you straight to the scree/client action.

Currently, entity actions in OutSystems update all columns of a record, even when only specific attributes need to be modified. It would be highly beneficial to introduce an entity action that allows updating selected columns only, similar to an SQL UPDATE statement. For instance, if I need to update only a user's mobile number, I should be able to pass the user ID and the new mobile number alone, without requiring the entire record. This approach would: Simplify the implementation. Improve performance by avoiding unnecessary updates to other attributes.

I have the need to organize applications and modules in multiple ways and want to be able to add multiple labels to the application. So that I can filter by label(s).E.g. label Orders to identify all modules that are in the Orders domain. Another label could identify the module layer and jet another one to identify the team responsible for the module.I would be great if there was a link to Discovery for these labels so that the architecture is defined inside service studio.

In the Test Query tab, there's a scrollable list of tenants sorted by tenant ID to pick which tenant to test a query with. That is fine with a dozen or so tenants, but we have a few hundred in our test environment and that list is impossible to deal with. The scrollable list should be replaced with a more robust search system... allow us to pick by name or tenant ID. J.Ja

Hello,In version 11.53.28 there is a new export image function for UI, logic and processes. This is a great future, however I feel like the position of the 'export x to image' button for actions should be changed. I believe that many developers are used to quickly adding input-parameters, which now leads to saving images. My suggestion is to move the export function down in the list, below the variables.

Like Traditional, Reactive should have "EmailId" return variable. Sometimes we need to save ".eml" content & share in network path, if specific environment does not have permission to send mail. Getting the content from Platform "Email Content" table with filtering does return correct content if we are sending frequent mail.