Regarding O11 and its caching capabilities (cache in minutes property on aggregates and server actions) it would be useful to have some metrics that allows us to understand the cache misses/cache hits or even cache miss ratio so that we validate if the cache in minutes property is being used wisely. The goal here is to catch the incorrect usage of cache in minutes, sometimes this feature is uses without doing the right assessment of data skewness and its usage. Sometimes the evolution and usage of the applications makes the business data to grow/change making the cache somehow less useful Having a cache with 70% miss ratio means we are missing the cache 7 out of 10 times, meaning, we are wasting resources (in this particular case, cache should not be used) Its hard to find which modules and core are using cache. Its hard to check the cache size. Providing this metric would allows development teams and CoE to have visibility on the cache usage and adapt

It is known that any Screen/Block in Outsystems Reactive can only be refreshed (when already instantiated) if an input parameter is changed of that Screen/Block.What about having a property in each Input parameter , saying: Reassigned to the same value  will trigger On Parameter ChangeHence, we could detect if any parameter is reassigned to the same value, and if it has that property set to 'Yes', the Screen/Block would trigger an On Parameter Change.

Currently, we need to manually create and implement audit trails for every data change (Create, Update, Delete). This process is repetitive, error-prone, and adds significant development time. It also leads to performance issues, bloats the AOs, and creates complex, hard-to-maintain flows. Solution: Automated and Integrated Audit Logging The proposed solution is a built-in Service Studio feature that automates the entire process. Developers would simply enable an "Audit Log" property on an entity. The platform would then: Automatically inject highly optimized, asynchronous logging logic into the entity's database actions. Handle all performance optimizations behind the scenes to avoid slowing down the main transaction. Prevent the creation of extra AOs, as the audit data would be managed by the platform itself. This transforms a complex, manual task into a single-click action, freeing developers to focus on core business logic while ensuring consistent, high-performance, and reliable data security and compliance.

Currently it is the case that the username for the developer is shown in the created by field for server actions etc. This can be confusing when the username is not in a readable format when it is forced by the company you work at. The name for the developer can be changed and should be readable.

When I edit or look up data during development with 'View Data' in my entity, the order of the attributes are so random. I'm getting pretty crazy of scrolling and searching for my attribute and it's value. (Especially in my 225 attribute entity! Yes, I could optimize) Why are the attributes not ordered by the way you ordered them in the entity? or at least on alfabatical order? Seems like an easy fix. Also what decides if a attribute is collapsed or expanded? seems random also.

 Problem When using Aggregates, OutSystems requires that all attributes in the Output must either be included in the Group By clause or wrapped in an aggregate function (Sum, Count, Max, Min, etc.). In many scenarios, developers need to group by a single attribute but also display other attributes that are functionally dependent on that group. Currently, this forces developers to either: Add unnecessary fields to the Group By (which can negatively impact performance and change result granularity), or Use artificial aggregations like Max() or Min() just to expose the attribute in the output. This creates unnecessary complexity and may lead to confusion or performance issues. Impact More complex and less readable queries Potential performance degradation due to excessive grouping Workarounds that do not represent the developer’s actual intent Additional learning curve for new developers Expected BehaviorAllow Aggregates to output attributes that are functionally dependent on grouped attributes without requiring them to be included in Group By or wrapped in artificial aggregation functions. Possible approaches could include: Automatic detection of functional dependencies (e.g., attributes from 1-to-1 relationships) A configuration option to mark attributes as dependent on grouped fields More flexible output configuration in Aggregates Use Case ExampleGrouping orders by CustomerId while displaying customer attributes (Name, Email) that are uniquely determined by CustomerId, without requiring extra grouping or artificial aggregation. Business Value Better performance practices Cleaner and more intuitive queries Improved developer experience Reduced need for workarounds

We all know that the Aggregate is not usable in some certain situations, for example when you want to use some extensions or when you have a DB fields encryption and so on.I'd like to have an option to transform an aggregate into an advanced query on my code, so I won't waste my time creating lots of joins and filters that I've already created on the aggregate.This would be really helpful and given that you generate the SQL code it seems pretty doable.Best regards,João Carreiro

I very much liked in former times the three developer classifications: Associate Professional Expert Professional has unfortunately disappeared now. I think the personal step from Associate to Expert, when setting career goals is a big one. The range from Associate to Expert is too big. I would very much like a reviving the professional status, after the Associate classificaton when a developer obtains any three of the six required additional certifications for an OutSystems Expert to get rewarded as "OutSystems Professional Developer"

Currently, developers receive community points for submitting Forge components from OutSystems 11, but no points are awarded when submitting from ODC. It would be great to align this with O11 and grant points for ODC submissions as well. This enhancement would motivate developers to contribute more reusable Forge assets in ODC, fostering greater community engagement and innovation.

During the development, when you add functionality through the editor view itself (not drag and drop from the Logic-Tab, stars are sparkling over the last added LogicNode. It would be great to disable that UX-Element, because als long as those stars are sparkling, you are not able to click the logic node below. This slows down the development speed. Thank you, Kevin