Currently, if we define a Sorting by an attribute, that sorting becomes unresponsive after introducing a Group By in the aggregate, as the sorted attribute is no longer part of the aggregate output . This does not raise any errors or warnings in the TrueChange Tab or any signaling in the workspace. I find that this is an easily overlooked situation that can lead to unexpected behavior or inconsistent results. I suggest the implementation of a typical Outsystems background validation that triggers a warning (written on the TrueChange Tab and a visual cue on the aggregate) whenever the aggregate's sorting references attributes that are not part of the aggregate output after a Group By, ensuring consistency and preventing silent issues.

During the Outsystems Usergroup at Nextstep 2019 in Amsterdam someone asked why the technical sessions weren't very technical or in depth. The reason for this is that there's a wide range of experience and expertise among the attendees of Outsystems and the technical sessions are open to all of them. This makes sense, but the short 20 minute sessions are hamstrung by having to go over basic stuff sometimes.Perhaps for the next NextStep you could implement some sort of complexity indicator for the technical sessions. For instance, associate and professional level technical sessions. This would allow the professional sessions to skip over the basics of development and get more technical or in depth on a specific subject.

I would like to see an accelerator in SS (and ODCS) where we could choose to create a timer based on the below template according to the best practices to ensure Data Integrity, Timeout Prevention, Completeness and Doesn't Repeat Work. One could customize it afterwards to his needs or simply choose the current option to create a timer with an empty canvas. The accelerator should also include a "KillTimer" Site Property in the flow to ensure there's always a way to stop a timer when needed.

What I like to see: switchto be able to set the labels of the conditions instead of seeing 1,2,3,4 and otherwise do/while/do or  for-loopI really would like to see a simple do/while on a condition, instead of a cumbersome if statement. the "cycle" note is a nifty feature with it.wether is should be a for-loop with just an integer or a do/while I don't mind.except for esthetics perhaps, because I don't like "breaking" out of a for-loop

Currently, when we send emails using OutSystems, it doesn’t return the email ID after sending. This makes it very difficult to track/identify which emails were sent successfully and which ones failed. For example, if we are send 100 emails every day, we have to rely only on the system entity to check their status. But there is no provision to link this system entity to our application's transactional entity, so it’s hard to identify emails with their purpose or origin. It would be very helpful if the SendEmail action could return the email ID as output. This way, we could link the sent email with our business entity and easily track delivery status for each transaction.

I would like to be able to consume REST API's with Swagger/OpenAPI version3 definitions. It would also be nice to be able to import YAML, instead of  only JSON.Another nice thing would be to be able to use API's documented via https://app.swaggerhub.com/ .

The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Here are some suggestions of improvement: 1. New Filter for Changed Elements When applying a filter to show alerts analyzed within the past two weeks, we sometimes still see alerts for elements that haven’t been modified in years. While older alerts are important, they should be reviewed in different contexts. A filter that displays only elements that have been actively changed within the selected timeframe would improve efficiency. 2. New "Brainstorming" State Some alerts involve complex issues where immediate fixes could pose risks. While the "Remind Me Later" status helps, some alerts need to be reconsidered at a later stage in the project without requiring monthly snoozing. Introducing a "Brainstorming" state would provide a clearer distinction for alerts that require further discussion before resolution. 3. New Filter for Unassigned Alerts Currently, users can filter alerts assigned to specific users, but there is no direct way to view alerts that have not been assigned to anyone. While exporting alerts to Excel allows for this, having an in-app filter to display unassigned alerts would be much more convenient and efficient. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

It would be great if OutSystems could provide its own AI solution, similar to Neo, to help developers implement AI-driven features securely within the platform. Relying on third-party AI integrations often raises concerns about data privacy and security. By offering a native OutSystems AI, customers would gain greater confidence that their data remains protected while still benefiting from AI capabilities such as automation, prediction, and chat-based assistance all managed securely within the OutSystems ecosystem.

A module in Service Studio will register a "change" when viewing data from an entity in some contexts, requiring the developer to either re-publish or to click "Don't Save" when closing the module: If a developer is only viewing data, no changes have really been made, right? I would prefer not to have to click this "Don't Save" button. Below are the different contexts I tested and whether a "change" occurred as a result. Option 1: "View Data" on a static entity on element defined in the module Result: no "change" Option 2: "View or Edit Data" on a regular entity on element defined in the module Result: no "change" Option 3: "View Data" on a static entity that is being consumed from another module Result: a "change" occurs Option 4: "View Data" on a regular entity that is being consumed from another module Result: a "change" occurs

Make it possible to consume Service actions from within a library. Within a library I can consume a REST API, but can not consume a service action. A REST API gives additional overhead in respect to a service action call, like additional authentication and autorisation. In a service action this is all safely handled by OutSystems.