Sometimes when the Aggregates have many entities and attributes it's hard to find a column/attribute.In my case, i had issues to find the column i wanted to group by and it took me a lot of time to find it.I think this idea can help improve the development speed.

Câmara Municipal de Cascais wants to develop a mobile App to be used by the citizens to donate money to be used to buy medical and emergency materials. The value that will be donated by the citizens will be doubled by Câmara Municipal de Cascais in an effort to further reduce the impact of the COVID-19 virus in the society

Hi everyone, I’ve noticed something with the "Duplicated Code" pattern in AI Mentor that has been causing a lot of false positives in real projects. Right now, the detection seems to focus mostly on the Action flow structure (basically the “shape” of the logic). The problem is that many Actions in OutSystems naturally share the same simple pattern, like: Start → SQL → Assign → End So even when two Actions have completely different SQL queries and return different Output Structures, AI Mentor still flags them as duplicated just because the flow looks the same. In practice, these aren’t duplicates at all. They just follow the same architectural pattern. Trying to merge them usually doesn’t make sense, can hurt readability, and sometimes even impacts performance. Suggestion It would help a lot if the duplication check also considered the SQL widget details and the Action contract, not only the flow. For example, avoid flagging when: the SQL statement text is clearly different the Output Structure is different the returned data shape is different Maybe duplication should only be reported when the flow and the SQL and the outputs are very similar. This would make the detection more semantic instead of purely structural. Benefits Reducing these obvious false positives would: • Reduces false positives • Less time wasted marking valid code as “Won’t Fix” or "False Positive" • Prevents unnecessary refactoring that may hurt performance • Increases developer trust and adoption of the tool I think this small change could make the Duplicated Code pattern much more accurate and much more valuable in day-to-day development. Thanks!

Now you need to create a public action if you want to reuse a screen action.Would be nice to have something like "public" screen actions

Currently, it's only possible to sort and filter in the ViewData Editor in Service Studio, and it shows the top X rows. Please add pagination to this view.

let the developer split the screen and allow to open several webscreens (tabs) of the same espace. something like the split screen and tabs on .net visual studio

It would be nice, that community members can start/read discussions on each training video page on the outsystems.com/learn site.So what I have in mind is a the page where the video is to have a discussion thread at the bottom of that page.

When working with Advanced SQL actions, there is the option to add test values to the parameters, and run the query with them. The executed query is shown in the "Executed SQL" tab, which is great. However, it would be very helpfull if that query could be extended with the parameters used. e.g. declare @company_id int; set @company_id = 3; SELECT [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] , [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[NAME] FROM [OSDEV1].dbo.[OSUSR_WU3_COMPANY] WHERE [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] = @company_id That would make it possible to copy the query with the used parameter values, and paste it in the database tool and be able to run it directly (instead of having to configure the parameters again). Please note that this is somewhat related to this idea, but I believe my suggestion is better: https://www.outsystems.com/ideas/8176/show-real-value-on-advanced-query-executed-sql/

We've seen a lot of discussion around Static Entities lately, for example, this idea . While Static Entities provide some value for enumeration use cases, they fall short in a lot of ways: They are stored in the database. They are expensive compute wise (more than they should be) to retrieve. They cost AOs. To use them on client side (other than the ID), they need to be manually synced. Developers need to understand the aforementioned details to use them correctly. Traditional Enums in high code languages are much better. They are directly in the code, making them available at no cost to the caller. Since OutSystems is a giant compiler, Enums should be a first-class construct that: Are compiled into constants rather than stored in the database. Are accessible both server-side and client-side without requiring manual synchronization. Do not consume AOs. Can be used in Service Studio like a variable. Maintain type safety like a Static Entity ID. Static Entities are an old primitive of the platform. I don't believe changing them at this stage is a good move, so I propose creating a new primitive—Enums—that align with modern best practices while keeping the low-code philosophy.

My idea is to have a Mentor (AI assistent) inside the SQL Editor in ODC/Service Studio to be able to use natural language to write SQL code. There could be an extra tab next to the current ones (SQL - Test Inputs - Test Output - Executed SQL) where you can ask Mentor to write or optimize your SQL code and set Parameters and Output Entities/Structures.