Currently, when a mobile or reactive app client disconnects mid-request (e.g. user backgrounds the app, loses network, or a timeout occurs), OutSystems logs the following errors in Service Center as 500-level errors: "The client is disconnected because the underlying request has been completed. There is no longer an HttpContext available." "Failed to send request due to unexpected error" These errors are thrown deep in the ASP.NET/IIS pipeline by the ErrorNotifierModule, below the OutSystems application layer. This means developers have no way to catch or suppress them using OutSystems logic — not through OnException handlers, not through error handling in Client/Screen/Data Actions, and not through any pattern available in Service Studio. Why this is a problem: These errors are not actionable by developers — there is no OutSystems-level fix that prevents them They pollute the error log in Service Center, making it harder to identify real application errors (we currently have an average of 60.000 daily errors like these) They generate false alerts in monitoring tools and APM integrations that consume OutSystems error logs They cause unnecessary noise in production environments, particularly for mobile apps used on unreliable network connections What we are asking for: OutSystems R&D to implement one or both of the following: Suppress specific known client-disconnect exception types (e.g. HttpException with error code 0x800703E3) in the ErrorNotifierModule before they are written to the error log, since these represent expected network-level events, not application bugs Provide a configurable filter mechanism in Service Center or Factory Configuration that allows platform administrators to define error message patterns that should be downgraded (e.g. to a warning) or excluded from the error log entirely Expected outcome: Developers and operations teams can maintain clean, actionable error logs that reflect real application problems — without being forced to implement infrastructure-level workarounds outside the OutSystems platform.

I have a scenario where I need to search multiple modules so each time I search I open the module and then search and option so its time taking, my suggestion is if I search module Camera I select it and search another module like Common so it open only Common module. This would be solved by simply keeping like multi select user search for the module and selects the module he wants to open and then there a list presented below the selected modules with search box open until user done with selection and when user clicks on open then all selected modules should open. I think that would be a much easier UX, both to implement and to present to the user.

I propose the development of the Outsystems Advisor , a tool designed to ensure adherence to Outsystems best practices. This solution will provide personalized recommendations to optimize deployments across five key pillars : Cost , Security, Reliability, Operational Excellence, and Performance.

Introduce a configuration mechanism that allows to enable or disable Code Quality analysis for specific applications and libraries. This capability would make it possible to exclude test applications, sandbox applications, or temporary applications, preventing them from affecting overall code quality metrics. With this configurable approach, we would gain greater control over which artifacts are included in quality measurements, ensuring that reports remain accurate, relevant, and focused on production-relevant systems.

I have two instances of Service Studio open, each connected to a different environment. When I do a 'Find Usages' on an element from Module A that is used in Module B (where Module B is only open in the other instance/environment), it points me to that other instance and it doesn't bring that Service Studio instance into focus. My idea is that Service Studio should open the module in the current instance instead, especially when the environments are different.

In OutSystems Platform publishing is like comitting your changes to Version Management. It would be extremely helpful to be able to add comments on the 1 Click Publish process. This would be even more flexible if one could drill down these comments by changed object (webscreen, webblock, action, webreference action, etc)

As we are now having folders everywhere, please do the same for service studio main screen. This way applications can be grouped by context.

On placing an element on the screen and filling, like a dropdown or a input that platform could provide a conventional name for the widget related to the variable name it is set. Instead of Dropdown1, it could be for example DropdownJobTitle if it is related to the JobTitle variable. Same applies to Buttons. This happens on the Input fields of the forms, when the form is auto generated with the Screen Aggregate.

Currently, when a developer enables a breakpoint in a shared environment (like Dev or Test), all active sessions hit that breakpoint. This disrupts other developers and interrupts their work. Introduce a "Debug My Session Only" toggle within Service Studio. When enabled, breakpoints would only trigger if the request originates from the developer’s own authenticated user session or specific IP address.

To add a link or a way to quickly open the Event Handler Action from Properties / Events of UI Widget. This can be extended to On After Fetch of Fetch Data From Server or UI Aggregrate. This will improve the developer experience to quickly open the Client/ Screen Action that assigned as Event Handler or After Fetch Event rather than scroll up and down Elements Tree For Button and link, we can quickly double click the Element in the canvas to quickly access the OnClick Event Handler already, however, this should be good if there's a similar way for other Widget like Dropdown, Switch, Custom WebBlock with Events, Data Fetch Aggregate...