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

 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.

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

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

In Q1 2022, I used SAP BAPIs to connect to SAP. However, I tried the ODC trial and there were no SAP BAPIs available. It would take a lot of effort from an ABAP developer to convert BAPIs to APIs. Can ODC have BAPI connectivity?

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....

My idea is to keeping the existing behavior but with the possibility to turn off automatic fetching data.Suggestion: Button like Test button (advanced queries) inside the aggregator to be able to disconnect or connect to the server.

Once in a while I have a project where 2 (or more) different types of users ( paid/free consumer/business etc) use the same application/flow/pages but require different styling.I know currently I can:- make different applications- make 2 flows- etcBut these options often result in doing double workSo I can:- Use a webblock with conditional css (not very pretty)- Use a class and write seperate code for each case in the css fileThe latter will result in unnecessary code in the css file (currently the best option I think thought)So it would be nice to have a (site property controlled) conditional theme. This way we can make a base them and then base the conditional themes on that.Alternatively allowing for SCSS would be a nice addition to create user personalized themes in your applications in a pretty way

At this moment, when we set the "Align" property of a container, it generates the align property in the HTML.Example:Align -> RightGenerates: <div align="right"></div>My proposal is to generate "system" classes the same way "OSInline" is added when a container doesn't have "Width" property set.My suggestion is (following above example):Align -> RightGenerates: <div class="OSAlignRight"></div>.OSAlignRight {    text-align: right;}.ar .OSAlignRight {    text-align: left;}The motivation:- I'm working in Arabic applications and it's a pain in the ass to go around that "align" property. Even after telling the whole dev team "don't use that crap, use our classes".Please, also update the SILK UI "out-of-the-box" RTL stylesheet to override this system classes.

When the Date Picker widget is placed inside a popup container, its calendar popup has a z-index that is too low to appear above the popup. In my application, the date field is mandatory, so this behavior acts as a blocker in the testing and validation process. Resolving this issue would greatly help developers during unit testing and proceed further.