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.

We would like to request the implementation of a Drag and Drop File Upload widget within the OutSystems platform. This feature would significantly improve the user experience by allowing users to easily drag files from their local system and drop them into a designated area for upload. It should support multiple file types and sizes, offer visual feedback during the upload process, and integrate smoothly with existing workflows. Adding this functionality would modernize the platform and align it with current best practices for user interface design

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.

Hello, If a certification with translation is scheduled, have the option during the exam to see the "original" question in English - in case there is any doubt about interpretation. When making a new certification available, disclose the dates that it will be available in other languages in the description, or have a standard deadline, (for example, 1 month after publication for Japanese, 2 months for Portuguese and 3 months for Spanish...), or the best option: only make a new certification available when it is already available in all languages. Thanks

Allow server actions and integrations (e.g. AI use cases) to stream text to the UI instead of waiting for the full response. This is standard on any AI powered app and since OutSystems is pushing AI features, I think this is a must have. We don't want our users to have to wait for the full LLM response before having some feedback. A way to implement this is to allow Server Sent Events which would even facilitate other use cases, especially in ODC with Event Driven Architectures.

 Problem : Right now, the platform lets us right-click an Entity and select "Create Action Wrapper" to instantly generate a secure CRUD wrapper. However, we don't have this option for Consumed REST APIs. Developers must manually create a Server Action, recreate the inputs/outputs, and add error handling for every single API endpoint. For large APIs, this takes a lot of time and involves repetitive boilerplate work. Solution : Add a "Create Action Wrapper" option when you right-click a Consumed REST API or its individual methods. When clicked, Service Studio should automatically generate a Server/Service Action that: Copies all input and output parameters. Calls the REST API method inside it. Includes a standard Exception Handler block. Why this helps: Saves Time: Speeds up integration development by cutting out repetitive manual mapping. Best Practices: Makes it effortless for teams to follow clean architecture guidelines by abstracting integration layers.

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.

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.

I am suggesting the addition of an IsAsynchronous parameter ( non-mandatory, set to False by default ) on the Refresh Data UI Flow Screen action, to tell the Refresh Data block to run the given Data Source in either an asynchronous or synchronous way, depending on the value of that input. This will spare the work of creating dedicated screen actions to refresh the Data Sources separately in a Screen Action to conceive a pure asynchronous Data Source Refresh, when applicable. Best regards!

Please add a native, fully supported platform feature to move an entity from one module to another without losing data. This feature should preserve primary keys, foreign keys, references, and runtime data, and it should update dependencies safely across producer and consumer modules. It should also support impact analysis and validation before applying the change, so teams can refactor module boundaries with confidence.