The Vision To create a seamless, AI-powered development workflow by embedding OutSystems Mentor directly within ODC Studio. This integration aims to transform Mentor from a separate assistant into an active co-developer capable of generating features in real-time through natural language prompts. Key Features Embedded AI Pane: A native "Mentor" sidebar within ODC Studio to provide contextual help without leaving the development environment. Prompt-to-Feature Generation: Enable developers to describe small features (e.g., "Create a CRUD wrapper for this entity" or "Build a validation action for this form") via text prompts. Automated Logic Injection: Mentor would draft the suggested Logic, UI patterns, or Workflows directly into the open ODC application for the developer to review and publish. Contextual Awareness: The AI should understand the existing data model and client-side logic to ensure generated features are compatible and follow best practices. The Value Add Increased Velocity: Drastically reduces the time spent on repetitive or boilerplate development tasks. Lower Learning Curve: Assists junior developers in implementing complex patterns by following AI-guided prompts. Reduced Context Switching: Keeps developers focused in a single interface, increasing overall productivity.

Right now, once a secret site property is created, you can’t see or validate the actual value—especially in production environments, where developers don’t have access and only a dedicated support team configures the values. This creates a risk: if the value is entered incorrectly, there's no easy way to check or confirm it. Benefit: It would help with auditing and validation. Teams could verify that the correct value is set, even in restricted environments, and avoid errors caused by misconfiguration. Thanks

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.

Recently I had a problem when updating the OutSystemsUI library, the version I updated had a bug. As I continued development, I only later realized that there were some misbehaving components, and I soon suspected the OutSystems UI update. This way I had to go back several versions of my application, to get back to the last version of OutSystems UI, without any problems. This can happen with any library, and without more serious scenarios. There doesn't need to be many versions available to choose from, I believe that between 3 and 5 would be enough.

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

Outsystems portal need to add some loaders, I click on buttons it takes much time to see any interaction in system that causes I click many times on it. it's given me negative imprecision and bad UX. also in create Case Screen error raised Twice, one during writing case details other after clicking next

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