Actually, I am here with one point might be this is the good place. If everyone think on my opinion (and agree than it will be helpful). I was trying, to convert my record list to excel and when I go to the selection of attribute, I am selecting everything (approx 40 attribute), after that got there is all attribute is already present which is good. But, we got that visibility first instead of last will be good (From my POV) .if anyone already know select ALL attribute is present then he directly select that. I also think crossly on this (as everyone everytime not select all the attributes). but still if, I need to select 40 attribute from 50 I can check first all attribute and then scroll done and remove the unnessary/unused attribute in the Excel. IF option is present and not visible first (at first instead I think everyone will get confused it is not a blocker but for user prospective I thought to give as an idea) Image Show all attribute after all the attribute

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:

You always have to use the Swap Connectors because True has to go down and False to the side for the exceptions.

The ability to assign customer icons to folders:

I would love it if I could open the widget tree in a new window similar to how you can with the aggregates. Here is the icon that will open the aggregate in a new window:

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.

When retrieving findings from AI Mentor Studio via the API, it should be possible to obtain the findings that were snoozed, as well as the user and the date when they were modified.

Update The Old Video Tutorials in Outsystem Guided path. For example in outsystem traditional guided path -> Master Class on Javascript and jquerytutorials videos are published in 2016 - kindly update that New video , Some time old video unable to understand . It will take more time to understand .Thanks in Advancekishorevijay

When we request a trusted badge review for a component in the forge, there is no way to cancel that request. There are many reasons why I would want to do that, such as: I made a mistake in the version I submitted I want a new version to be reviewed instead of the one I submitted originally I received feedback from other components and now I know that my other requests will be rejected for the same reason. Being able to cancel in these situations would remove work from outsystems staff

This is just a small detail, but when we have a big For each label, it will be overlaid with the "cycle" label.The improvement idea was to center the label cycle across the arrow.I have a screenshot attached.