In ODC "Add Public Elements" should be similar to O11 "Manage Dependencies". Or, at least, the user should be able to choose between using the new "Add Public Elements" and "Manage Dependencies" with the O11 like visuals and functionalities. In ODC the information provided and selection of Public Elements it's time consuming and developers cannot have proper control on the overall picture. In O11 developers have more control when using Manage Dependencies and can quickly understand what is happening. ODC: O11:

If you go to your customer portal, and you have a corporate infrastructure/environment and a personal environment, your personal environment is AWOL in the interface. Please can it show ALL infrastructures/environments please?

Breaking into tech is tough, especially for entry and mid-level developers who need experience but struggle to gain it without opportunities. What if we created a community-driven challenge where developers build real, useful applications or Forge components that benefit the OutSystems ecosystem while advancing their careers? How It Works Participants can compete solo or in teams, allowing both independent developers and collaborative groups to showcase their skills. Categories include: Application Development – Build fully functional apps that solve real-world problems. Forge Components – Create reusable components that improve development efficiency. UI/UX Enhancements – Design intuitive, accessible interfaces that elevate user experience. The event fosters friendly competition, networking, and hands-on learning. Winners (or standout contributors) receive certification vouchers, accelerating their careers. Why It Matters Bridges the experience gap: In the US, it's difficult to find work without prior experience—this provides tangible projects to showcase. Boosts OutSystems adoption: By targeting aspiring tech professionals, this event could introduce new talent to the platform and generate buzz in the job market. Grows the Forge & community: High-quality contributions enhance the OutSystems ecosystem, making it easier for everyone to build better apps. Additional Challenge Features Mentor guidance from experienced OutSystems developers. Themed challenges (e.g., accessibility, AI integration, automation). Judging criteria based on innovation, impact, usability, and scalability. This initiative could be a game-changer for developers looking to break into tech while also strengthening the OutSystems brand and community resources. Would love to hear thoughts from the community on this!

Today, AI Mentor (App Generator) is powerful when it comes to validating best practices, architecture, and quality of applications already developed in OutSystems. My proposal is to expand this capability so that the Mentor can read external source code (for example, from a Git repository, in languages such as Java, .NET, Node.js, Angular, etc.) and: Analyze the structure, business logic, integrations, and existing architecture patterns in the legacy code. Automatically suggest how this code could be rewritten in OutSystems, following modularization, security, and scalability best practices. Generate initial components (entities, actions, APIs, UI blocks) inside an OutSystems module as an acceleration base for migration. Value for the Community and Customers Accelerated migrations: companies with legacy systems could move to OutSystems much faster. Reduced risk: the process would become more predictable and auditable. Productivity: developers focus on evolution instead of manual migration work. Governance: the automatically generated application would already comply with AI Mentor’s best practices. Example Use Case Migrating a management system in .NET/SQL Server to OutSystems. AI Mentor connects to Git, reads the code, identifies entities, logic, and integrations, and suggests a skeleton in OutSystems that developers can refine. Expected Impact Disruption in the modernization process of legacy applications. Competitive advantage for OutSystems compared to other low-code platforms. Faster adoption of the platform by large enterprises with extensive legacy systems.

Hospitals will start having issues with ventilators during this high usage times that are approaching. After doing shifts for more than 48 hours it won't be easy for medical and technical staff to properly troubleshoot the cause.For instance, sometimes ventilators stop working and the problem is the UPS. What needs to be done is simply connect the ventilator to the energy outlet rather than the UPS.The purpose of this system will be to allow technical staff to submit issues with ventilators (by brand and model) and have specialists indicating possible solutions.

Hi, Recently I have uploaded an asset to the forge. This ideia came up to me because I felt the need to see a progress tracker, that indicates in which state the upload is currently on. By implementing this, the user always knows what is happening behind the scenes and avoids contacting the support to know more information about this. It would save some workload as well for the support members. Best regards, André Almeida.

Everyone knows that descriptions are helpful to understand the meaning of a variable or anything. My suggestion is to show the site property description in the lifetime as we can see in the service center.

Hello. I believe that we could have a new option to S ort by on OutSystems Forge: Component Creator and this option could be send to OutSystems Profile of the OutSystems Developer . Best Regards, Paulo Russo .

Like one can move a single statement down in the Assign node, it would be very helpful to add the ability to move a node up or down in the logic flow.E.g. if I have an Assign node and then an Aggregate node and I want to move the Assign to rather be after the Aggregate - it would be a time saver to be able to click on the Assign and use some shortcut to make it move to after the Aggregate immediately rather than disconnecting it and moving it manually.

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 :)