Currently it is the case that the username for the developer is shown in the created by field for server actions etc. This can be confusing when the username is not in a readable format when it is forced by the company you work at. The name for the developer can be changed and should be readable.

Hello everyone, I’d like to suggest implementing a mechanism for approving forum solutions. With more and more community members actively contributing and answering questions, it would be valuable to have a way for a champion, MVP, or staff member to officially approve a solution and/or provide authoritative feedback. This could include notes such as suggested improvements. I believe this would be especially helpful for newer or beginner members, who may not yet have the experience to evaluate multiple answers and might default to the first response, even if it’s not the most accurate or optimal one. Such a feature would help ensure higher-quality guidance across the forum and make it easier for users to identify reliable solutions. Additionally, there are many older topics that have received answers, but the topic creator never officially marked a solution or confirmed whether the answer worked. This often leads to members replying to old or inactive threads, which can unintentionally push newer and more relevant topics down the forum list. I’ve seen cases where newly created topics end up on the third page of the forum because multiple old threads were resurfaced. With an approval mechanism in place, moderators could review these older topics and officially approve a solution where appropriate.

let the developer split the screen and allow to open several webscreens (tabs) of the same espace. something like the split screen and tabs on .net visual studio

If a developer uploads a forge component, that has dependencies for other forge component, and that component is owned by another developer. When changes is applied to the dependencies like: discontinuing the consumed version, uploading a new version to fix issues, ... etc. Let the consumer know that changes had been made, to upload new version of their asset if needed.

Add disabled input for wizards - Currently, when using a wizard or wizard item, it is necessary to use logic or if statements to disable a wizard step (if validation is required for the user to proceed to the next step). There is no "enable" input like in other OutSystems UI widgets. So, if "enable a true" it was possible to click on the wizard item icon, and if "enable a false" it blocked the click. NOTE: I'm not looking for help to solve the problem. It's just an idea for improving the widget (in O11 and ODC). Thank you :)

After generating the application in the Prompt, you can keep the prompt active to add new items and also edit something that has already been created. Always leave the prompt active to request new resources or edit them, modeling them as needed.

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.

What if OutSystems had a Model Context Protocol server available? Ultimately could support external applications to articulate the platform, but, until it gets there (if it gets there :D), for the use case I am looking at, it could allow me to extract structured business knowledge embedded in the applications' models, including: Business rules and their interconnections Process flows and decision points Entity relationships and domain concepts Service dependencies and integration points ... Generating contextual documentation explaining how components work and why they were designed that way (and this is not a new idea) would be really helpful.

Migrating to ODC from O11 is very complex and tedious, This has lots of risk involved doing it manually. Migration with the LLMs and AI agents can automate the process and can achieve faster time to market. This could be beneficiary for everyone who want to migrate to ODC.

An integrated " AI Audit Trail ." that attaches the original natural language prompts and business requirements to every generated element. This would allow the architect to click any logic node and see the" intent history," helping to debug AI " hallucinations" in complex business rules.