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.

When we do a merge with two OML, would be useful to have a search box to filter whats been shows in Compare and Merge box.

Dear all,The AD has a chart with the overall technical debt trend for all applications within Outsystems factory, however should be very interesting to have something similar for each application.Something like:Best regards,João Paulo Pires

When I try to use the built-in action ListAny in a client action that needs to be a function, I currently get the error message sayingOnly actions that are functions can be used in other functions.From the documentation I get it that you don't want to perform asynch or server calls within a client function, but surely ListAny (or any other 'harmless' action) should be allowed?Or, at the very least, please make a function version of the built-ins ListAny, ListIndexOf and ListAny available.

I would like to suggest improving the loading animation in the Service Center when applying filters or performing actions. Currently, the indicator is barely visible and only appears if you scroll down, which makes it difficult to know whether the system is processing, still loading the filters, or if the action failed. At the moment, there is only a small loading bar that becomes visible when scrolling. A clearer solution could be to add a button‑loading or a loading indicator next to the filter button, so devs have immediate feedback that an operation is in progress. Filtering: Loading not visible The red loading bar at the top only becomes visible when you scroll down.

Hi guys, we use something similar here, but we do it manually.We know that good architecture is very important in our projects. It is a wonder if we could see in our tree view the actions and other dependencies with the same color they were classified in the discovery tool.For instance: library modules can have the default icon green and core modules a default color orange.So, when you are in a green module and try to consume an action from the core module, you can see you are doing something wrong directly on your tree view and safe time to run the discovery and check this later.Even the developer who is not so expert in 4LC can help to keep the architecture in the right lines.

OutSystems Reactive Web Apps that allows developers to define a global Client Action "Global OnBeforeNavigate" (or Server Action) that executes before navigation to any screen. (In Reactive - At least On before request of server & Service action, allows to add custom logic validation, Authentication, etc) This acts as a centralized "middleware" or "router hook" similar to ASP.NET Core Middleware Currently, OutSystems developers must manually call shared actions in OnInitialize of each screen — which is error-prone, repetitive, and unscalable in large apps. Adding global lifecycle hooks brings enterprise-grade control and flexibility to navigation handling — making Reactive Web development cleaner and more maintainable.

It could be useful the existence of a kind of widget , similar to the page count richwidget, focus to the creation of reports (with auto pagination, Header repetition, SusTotal, total, ...) to be printed .

When are we gonna have a option to access the metadata from a OML file?In my case i need to generate report for instance, all screens and their input/output parameters to a given Espace.This information exist only in the OML file. Therefore only the Service Studio is able to open it. Maybe some component which could translate it?I think its important feature for enterprise grade Frameworks like Outsystems.With best regards,Slavi Popov

While using the Upload widget, it would be really helpful if there were built-in properties to set allowed file types (like .pdf, .jpg, .docx, etc.) and a maximum file size limit (in MB or KB). Right now, we have to write custom logic or JavaScript to validate these things, which takes extra time and can be tricky for less experienced developers. If these options were available directly in the widget, it would save time and make file uploads more secure and user-friendly out of the box.