Hello, It once existed... but it doesn't anymore. https://www.outsystems.com/ideas/1673/bundling-and-minifying-the-javascript-css-files/ When we publish a solution that has a mechanism to minifying CSS and JS - well, it could be a checkbox that the user chooses whether or not they want this option, and it might not be available in the free version... But that could benefit the performance of applications.

Looking at the authorizations offered while creating the connection to MCP (Model Context Protocol), all the options related to (OAuth) ask for a client secret as a mandatory field. While searching on MCP Documentation, the client side must implement a PKCE (Proof Key of Code Exchange) flow, with this flow its not mandatory to have a client secret to get Authorization to interact with the MCP Server. Making a lot of MCP Servers impossible to connect to OutSystems. Where is the link for the documentation where they explain why PKCE flow should be mandatory: https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#authorization-code-protection My suggestion here is to make client secret not mandatory.

When working with Advanced SQL actions, there is the option to add test values to the parameters, and run the query with them. The executed query is shown in the "Executed SQL" tab, which is great. However, it would be very helpfull if that query could be extended with the parameters used. e.g. declare @company_id int; set @company_id = 3; SELECT [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] , [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[NAME] FROM [OSDEV1].dbo.[OSUSR_WU3_COMPANY] WHERE [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] = @company_id That would make it possible to copy the query with the used parameter values, and paste it in the database tool and be able to run it directly (instead of having to configure the parameters again). Please note that this is somewhat related to this idea, but I believe my suggestion is better: https://www.outsystems.com/ideas/8176/show-real-value-on-advanced-query-executed-sql/

It's always a problem when users click on buttons more than once, duplicating server requests. There are solutions for both client and server-side.

Rank the badges on the certificates, instead of just showing them by date. Put the expert/Professional badges at the top, making them bigger, possible with a line under that section, and don't show the lower "Associate" certifications that they supersede, or put them smaller at the bottom: (They are only at the bottom in this example because I passed them first.) Thus:

Hi everyone, I’ve noticed something with the "Duplicated Code" pattern in AI Mentor that has been causing a lot of false positives in real projects. Right now, the detection seems to focus mostly on the Action flow structure (basically the “shape” of the logic). The problem is that many Actions in OutSystems naturally share the same simple pattern, like: Start → SQL → Assign → End So even when two Actions have completely different SQL queries and return different Output Structures, AI Mentor still flags them as duplicated just because the flow looks the same. In practice, these aren’t duplicates at all. They just follow the same architectural pattern. Trying to merge them usually doesn’t make sense, can hurt readability, and sometimes even impacts performance. Suggestion It would help a lot if the duplication check also considered the SQL widget details and the Action contract, not only the flow. For example, avoid flagging when: the SQL statement text is clearly different the Output Structure is different the returned data shape is different Maybe duplication should only be reported when the flow and the SQL and the outputs are very similar. This would make the detection more semantic instead of purely structural. Benefits Reducing these obvious false positives would: • Reduces false positives • Less time wasted marking valid code as “Won’t Fix” or "False Positive" • Prevents unnecessary refactoring that may hurt performance • Increases developer trust and adoption of the tool I think this small change could make the Duplicated Code pattern much more accurate and much more valuable in day-to-day development. Thanks!

When developing large applications in Reactive, it is not a good practice to have all screens in the same module, otherwise its size grows considerably, taking a lot of time to open and to deploy. In those situations, it is common to split the screens through different End-User modules.At this moment for Reactive applications, it is not possible to control the module name in the URL, without being through changing the module name. This is not ideal, because the module respects a naming convention according to the factory governance, for instance <Business Application>_<MainConcept>. Besides the name the module appears in the URL is usually lower-case whereas module names are usually camel-case.Being that said, I think it would be nice to have the possibility to define the module SEO name, just like it is done for pages in Reactive Applications. This is a feature from Traditional Web that does not exist in Reactive and it's unfortunate that one has to change the name of the module from MyApp_Support  to support , for this purpose, going against our governance and architecture naming convention.

Hi, I'm not sure if I'm the only one experiencing this but my login in outsystems.com does not persist more than a couple of hours even if I have the "Remember me" option enabled. Furthermore, I have to type mail email every time as my browser does not offer autocomplete for the email input (this might be a separate issue). Even when I try to access documentation pages, it asks for my login. If I refresh a couple of times I can access them without session. So clearly something is very wrong with the login system in outsystems.com . Could this be improved / fixed? Thanks, Tiago

Currently if you have two OutSystems applications, one that exposes a REST API method and the other that consumes the method, in the consumer application you can't see if the method was changed in the exposing application and refresh it.It would be a good idea to have a "refresh REST API" option that refreshes all the consumed methods from a REST API, like we have for SOAP services (see attached image). Also, to have a warning message in a consuming application that "method x" was changed and you need to refresh that method.For example, you have a method without input parameters that returns a list of records and you consume it in another application. If in the exposing application you add a mandatory input parameter to the method and then run the consuming application you will get an error message because your request to the service is incorrect.When you open the consuming application in Service Studio you don't get a warning that one of the consumed methods  has changed and you don't have an easy way to update that method. You have to remove it and then consume it again and for this you need to know what was changed in the method.

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.