With REST services, we can open the documentation from the context menu. With SOAP web services, we have to type the URL (which is not easy to find) to get there. It would be great if we had a context menu option "Show Documentation" for SOAP as well.

It's good if we have option to share our achieved badges to social media like LinkedIn. Whenever we achieved a badge in mail as well as the profile page , it's good to have a share action. By showing it to outer world, it's showing our achievement as well as it will create enthusiasm among others who watching this post in social media. So I think it will be better to have this feature in OutSystems. Regards Murali

 Add a possibility to do a Distinct Select from a field on a Simple Query.

When exposing a REST API, OutSystems generates a swagger.json documentation for the endpoint. Used data structures are documented in the "definitions" section where their required attributes are listed by their name in the array called "required". Because the swagger file is mostly relevant for systems other than OutSystems, the internal name of the OutSystems structure is not of interest. Instead the required attributes should be listed by their JSON name like in the "properties" section:

Hi Team, As having more dependencies increases the size of your Module and increases the duration of 1-Click Publish.It would be great if user get warnings in TrueChange to remove all unnecessary dependencies of module.As of now i don't get any clue that no of unused dependency in module has increased to  a large number.Thanks,Preeti Kumari

Add support for string formatting in Expressions like python code.In Outsystems we have something like this:"My name is " + Name +" and I'm from  "+CityMy ideia is to implemenmt something like this:"My name is %s and I'm from %s " % (Name, City)

The debate about the null values is still alive and kicking in the OutSystems community. This shouldn't be a "war" between team No Null Values and team Null Values. Null values do exist in other platforms and they can't simple be ignored. It's not the first time since I work with OutSystems that I need to differentiate between a 0 and null values. Of course there are some workarounds, but are they the best approach? I don't think so. What if we could settle this "battle" once and for all? I propose giving developers the power to decide if null values should be the default for an attribute when creating it. Attribute per attribute. There could be an extra option in the attribute property, bellow "Default value", a checkbox with the label "allow null values". Always unselected by default. Simple right? And this is a common option in other platforms. It sounds reasonable to me and may solve the "war", as everyone can have their predilect choice.

Like ListClear action there should be one for records. With just one action and just passing the record name as argument it could set the record attributes to the default values. This would be easier, faster and much cleaner than setting all attributes one by one or assigning the record to a blank one.

By default OutSystems parameters are by value, but there are few exceptions. These exceptions should be visible at Service Studio.Example currently:Following would be better, when actually it is by reference.

It would be great if OutSystems exposed REST APIs supported multiple response types, instead of just one type (structure).In swagger, you can set a response type for each status code and have different structures for each one and all the different outputs are then properly documented.Something like this:responses:        200:          description: An array of products          schema:            type: array            items:              $ref: '#/definitions/Product'        default:          description: Unexpected error          schema:            $ref: '#/definitions/Error'This would give:- more flexibility when creating exposed REST APIs;- multiple response types support in the "OutSystems way";- better documentation, including all the response types available;