There are similar names in the community and I did notice that some developers can also get confused on who to tag. Or will have some hard time finding the person to tag. It did happened to me a few times. If we can maybe have a tag suggestions, probably will suggest those names first that are already in the conversation, then I think it can help in some ways.

As someone who always has a lot of tabs opened, it would be awesome to have the option to install the ODC Portal as a PWA.

As of now OutSystems Community profile score is based on user participation in forums, training, sharing ideas and forge. I know many leaders who are contributing for Community Growth via usergroups. Also many users actively participating in usergroup session. If we allocate some points for usergroup activities (organizer, speaker, quiz winner, participant ) it will be great. Just a wish 🙂

I would like to be able to add comments to True Change warnings when I hide them, so the other developers on the team know why I hid them. For example, if I make a mandatory field non-mandatory, and hide the warning, I want them to know what my reason is so they do not just change that setting. We have had a number of problems in the past because someone followed True Change warnings when they should not have. :( J.Ja

When viewing data in a table add a default sort so that the last entries appear first.I believe most of the times the developers want to see the last inserted items in an entity.At least, when I do "View Data" I always end up adding the sort...Edit: It could be an option in Service Studio.

When I was looking at the download page, I noticed two version naming systems are currently in use:For the IDE, on the downloads page we see the release "tag" (eg: "Development Environment 11 - Release 12").But then, on studio, we see the version number (eg, "11.0.406.0")Again, with platform server and lifetime this scenario repeats: on the download page the tag, on the software the version number. This creates a bit of confusion when one is trying to understand, e.g., which version of the platform server to download.By looking into this article detailing the version naming system and this article detailing the release lifecycle, one can reach the conclusion that the tag on the download page refers to the release life cycle ( the when ) and the version number details the type of changes on the release ( the what ).My suggestion is first and foremost to use a single naming system both on the software and the website, to avoid confusion. But going a little bit further, I would suggest adopting a simpler system where version number is based solely on the release (which in the end is the only thing the user cares about).  If as the article I previously linked suggests, there is predictability on the release cycle, then similarly to Ubtuntu, one can even make the date part of the versioning system, naming both the release and the version after the date, and if necessary, additional numbering for minor patches.Additionally, it would be really, really nice if we had exactly this page , but with the download links on the tables.Thank you for your time,Filipe

please add auto adjust action flow

In Service Studio or even in OutDoc to be possible to search and find all the Advanced Queries/SQL used in one module/eSpace.

It would be great if the reactive data grid provided associative columns or dependency between columns.For example, there are two dropdown columns, one called Function and the other called Role. When a Function is selected, the dropdown Role will display only the roles belonging to the selected Function.I think it is a very important functionality, used in a lot of cases, so it would be very good having it in the reactive data grid.Thank you

When we are comparing and merging 2 modules, it would be great to have a search bar (like we have when adding/removing references). When we have a lot of changes this could be helpfull, if we just wanna compare a specific action....