Inconvenience:If a user is having multiple accounts, they can very well able to link their primary account with their secondary accounts, but their community ranking doesn't get linked. because of this the ranking gets disturbed.Idea:In order to maintain proper ranking, Outsystems can provide an option called "Merge Ranks". By using this, the rank of the primary account will get reflected in all the linked accounts. So that, the secondary accounts won't disturb the ranking order. If user is not interested in merging their ranks, then they won't opt for it.

From what I’ve seen online, the main barrier preventing many companies from starting to work with OutSystems technology is the price of entry. I’d like to suggest introducing a new licensing tier with limited resources, but sufficient to run a real application in production. The goal is to enable smaller companies to deploy a fully functioning app, not just for testing, but in a live, real-world environment. This would make it much easier to demonstrate the true value OutSystems can bring to a business. Even with reduced resources, no high availability, and community support only, the ability to run a production-grade app could help change the perception of the platform and significantly increase adoption, especially among smaller companies and innovation teams.

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

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

Can we have a feature to view the history of resolved technical debt in AI Mentor Studio? This should include details such as what was resolved, who fixed it and marked it as resolved, and when it was resolved. And export as Excel.

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:

The ability to assign customer icons to folders:

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.

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.

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: