when refactoring entities between espaces, manual database scripts are required to migrate data to the new physical entity

I would like to be able to use HTML content in the email body in Reactive apps.Html content is needed to sent emails with a nice layout from Reactive apps.Expressions in Traditional Applications have the "Escape Content" attribute. When you set it to "No" a mail sent by a Traditional Application is delivered as a HTML Document. This is not possible in Reactive applications.The HTML Element can also not be used in an email in Reactive app.The only current solution would be, to create a Traditional Application just for sending the email and provide a public EmailSend-Method. But that is a lot of overhead just to send a mail.

Maintaining accurate, up-to-date documentation remains a challenge in enterprise environments — especially as applications evolve and team members change. While tools such as OutDoc provide valuable metadata-based documentation (e.g., structural elements, entities, modules, dependencies), there is an opportunity to extend documentation capabilities further using AI within the platform itself. I would like to propose native AI-generated documentation that goes beyond structural metadata and instead leverages the platform’s understanding of: Application logic flows Business rules and decision paths Integration intent and usage patterns Architectural layering Cross-module interactions Rather than simply listing components, the AI could generate contextual explanations such as: What the application does functionally How key processes are orchestrated Which integrations are critical and why How data flows across modules Where architectural boundaries exist This could live within the application overview, Service Studio, or a dedicated Documentation view — refreshable on demand and editable as needed. Importantly, this would add value not only for future platform directions, but also for the large base of existing OutSystems 11 (O11) applications running in production today. Documentation drift and knowledge loss are challenges that exist now, and having AI-assisted documentation available in O11 would provide immediate impact for enterprise teams. Many teams already experiment with exporting artifacts and using external AI tools to generate higher-level documentation. I recently explored this approach externally as a proof of concept: 👉 https://www.acceleratedfocus.com/post/bringing-clarity-to-undocumented-outsystems-code-with-ai Embedding this capability directly into the platform would: Improve developer onboarding Reduce knowledge loss Support governance and compliance Accelerate modernization initiatives Strengthen long-term maintainability This would not replace structured metadata documentation tools like OutDoc, but would complement them with AI-driven contextual understanding.

It would be nice to have an option to clone/duplicate an application in Service Studio in the application detail view like we have the option to edit and remove.And also it would be nice to have the option to do the same to the modules inside but as an option.

Service Studio should have new, separate "Tests" tab.This would enable integrating tests to any eSpace and would minimize required overhead for testing any action, including private actions.Why?Testing your code is more professional than not testing.Unit testing should be minimal extra effort for developer, because otherwise tests are usually not done.Publishing new code could be controlled - you cannot publish untested code, or code which has some failing tests, for example.Test code should never go to Production environment.Testing is good.How?Tests are integrated to eSpace/module oml file.During code generation process, actions from "Tests" tab would create a separate .NET project and this project would be a friend assembly (internalsVisibleTo attributes configured) for main project to compile.1-Click Publish deployments with tests could start from (currently underused?) personal area (or another IIS folder), where tests would be run.Depending on how tests go and how is decided in additional configuration, deployment would continue to Public area or show an error in Service studio.This way, creating unit tests would be as effortless as when creating unit tests in any other modern programming language - just few clicks away. There could be also accelerators to generate unit test actions or "system events" to initialize/teardown test runs.Currently, writing any tests to private actions is also either impossible or exposing some unwanted/test related code to production environments.It's a big change, but from discussions with makers/experts @ ODC I've learned this should not be too far-fetched idea to implement. Maybe for P12, please?Another, possibly the simplest way to enable testing / production code separation without massive modifications to existing compiling process could be a capability to define another espace as " friend " espace. This per-espace setting could reveal internal (=OS private) actions to the another espace marked as a friend and thus enable referencing these otherwise out-of-the scope actions for testing purposes.If done like this, feature could be achieved using small amounts of .NET reflection trickery or previously suggested InternalsVisibleTo attribute (that has been around since 2002 release of .NET 2.0).Security-wise, there should be no problems either, (albeit a bit more work during compilation) as friend assemblies can be defined as signed assemblies, too.Personal opinion, but this topic is really heavily connected with OS small book #2, #5 and #7.

Would be a (minor) quality of life feature if you could bind a label to an input if you simply drag and drop it from the tool box on the left straight on the Input widget. For example here, this widget is bound to a "Max records" local variable, to control how many records an aggregate returns. If I drag the label on to it, it could do several things: Add the label on top of the Input Set the Input Widget automatically on the Label properties, and give it a name like "InputName_Label" Set the text for the label on a 'best guess' case, depending on what the input is bound to (for example here, Max records) This could work for all other input type widgets: text area, switches, checkboxes, dropdowns, etc.

 To be able to set conditional breakpoints instead of breaking everytime.

If this is possible, I'm not seeing it. In O11 you can download a forge component without having to install it. In ODC this seems impossible. Why? I want to see what's in a forge component before committing to installing it in my environment. I have done this for as long as the forge exists. Why would you take away this option?

It would be nice if OutSystems provides us with an instruction guide or video on how to implement an existing reactjs component in OutSystems reactive app or library module. There are many react UI components available for example to show data in a tree, that are not implemented in OutSystems UI. Using as guide on how to do this, the community can extend the usability of the reactive web development more easily.

Implement an active Artificial Intelligence prompt directly integrated into Service Studio / ODC Studio, capable of analyzing OML files to detect issues, suggest improvements, and propose corrections , both automatically and through clear, detailed explanations of the proposed solutions . The idea is to allow developers to select a module or a set of elements (Actions, Aggregates, Entities, UI, integrations, etc.) and request an intelligent analysis that can: Identify logic, performance, security, and best-practice issues Suggest architectural and code readability improvements Clearly explain the root cause of each issue and the recommended solution Optionally apply automatic fixes or generate assisted refactoring suggestions An initial approach could involve exporting the OML for analysis by an external AI model (such as ChatGPT or Claude). However, the key differentiator would be having this capability natively embedded within the Studio , removing friction from the development workflow and improving application quality directly during development. Modern development tools already leverage AI for code review, refactoring, and optimization , delivering measurable gains in productivity and code quality. Bringing this capability deeply into the OutSystems platform would deliver significant value to developers , reinforcing OutSystems’ position as a leader in intelligent, AI-assisted low-code development.