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

When you're making changes in a module that sits low in the architecture canvas, you need to  manually republish many modules up the layers before you're able to test your changes.It would greatly reduce the pain involved if we could create something like a "1-Click Publish queue" in Service Studio and add modules to it. Then, with 1 click, SS would publish the modules in the queue in the order they were added.Suggestion: select the modules in SS with Ctrl+Click, right click, then "Add to new queue".

IDEs typically provide an option to customize code formatting.Service Studio lacks that functionality, which forces developers to format the codemanually.It would be great to customize the way that the code is indented. For example:Define the x and y coordinates of the Start NodeDefine the x and y coordinates of the Exception Handler (if more than one is present, align it to the right or to the left)Define the horizontal and vertical distance between nodes (in grid points)More advanced options could include, for example, if the first For Each node should align to the right or top right.A shortcut (e.g. CTRL + SHIFT + F) to format the code would also be great!Configuration example:Before:After:

I think that will be a good idea to receive points for each certification attained.It's a way to reward the effort of getting a certification and in my perspective it doesn't make much sense to get points for watching videos and not getting points when we pass a certification.Best Regards,João Fernandes

Hello,Our community forum has become a good platform where lots of problems are getting solved every day. Almost every day I spend some time to look for an activity happening around the forum, and I literally learned so many things from reading it, replying it.However, I was wondering if we can have mobile app design for our community forum. I know we can access our forum site on Mobile since it’s responsive, But using a mobile app is different and quite handy. I hope you will with agree with me.Regards,Sachin Mahawar

Dear OutSystems Training and Certification Team, As the OutSystems platform continues to dominate the enterprise low-code market, more organizations are leveraging it to build highly visible public-facing applications, B2C portals, and marketing sites. Because of this shift, Search Engine Optimization(SEO) has become a non-negotiable requirement for many development teams. I am writing to formally propose the creation of a new specialization badge: Outsystems SEO Specialist. These specializations would validate the developer's ability to navigate the unique SEO challenges present in single-page applications(SPAs) on both Outsystems 11 and ODC, covering critical platform-specific implementations such as: Configuring clean SEO friendly URLs and site rules Integrating third-party pre-rendering services like prerender.io effectively. Managing crawlability sitmap.xml and robots.txt with the constraints of ODC and CDN layers. Optimizing core web vitals and DOM loading structures specific to reactive applications. By creating this badge, OutSystems will empower developers to build applications that are not only highly functional but also highly discoverable. Thank you for your time and continued effort to expand the ecosystems learning path Best regards OJJallow

 With reference to this thread: https://www.outsystems.com/forums/discussion/31032/analyitcs-mobile-apps-in-lifetime/Currently, lifetime Analytics only reports on web applications.Please, enable reporting for mobile application on the server and network tabs. It is understandable that the client side of the mobile application would be difficult to report.This functionality has been needed since P10 and is critical to delivering on the promise of platform analytics.There is also an expectation being set on lifetime Analytics when the "Network" tab is selected: "Data collected when applications are running natively on a mobile device"It would be great if the following information was made available:Device type (tablet, mobile)Network type (3G, 2G, the other G, wifi, slowfi)OS Type and version (the 2 usual suspects)Browser Type and version (webkit, blink, etc.)Initial splash load timeEverything else that is reported on the server side for web applicationsThanksOuen

In aggregates when we pull an entity, if the platform thinks it should take other entities behind, it takes automatically, and also creates joins automatically. However, these "extra" entities are not always needed. So my idea goes through when we delete an entity from an aggregate, the joins that are created automatically, are also automatically eliminated. It makes it a lot easier to use.

In O11 we can end other debugging sessions by republishing the module. However, this does not work in ODC. It would be nice if there is a button next to each "active session" in the Users section of the Debugger tab in ODC Studio. With the click of the button, the debug session of the other account would end. This way, we can make sure that the app continues running normally without hitting the debugger activated by other accounts, in case the other users are unable to end their session. Security-wise it would be nice to give this option only to organizational accounts with elevated roles, e.g. the tech lead role.

In the OutSystems Community, it can be interesting to have a notifications bell in the header, between the search icon and the profile.We should receive a notification when we are mentioned in a comment, new comment in my post, kudos, etc etc. Also, the notification should have a redirect link to post/ideia/ etc.Like this:Thanks