Have an additional tab next to "processes/interface/logic/data" with application/module notes/comments made by devs.This would not only contain the "ToDo" post-its but also general comments about the module that don't have a particular screen. With possible links to code/actions.This way when working together there is a centralized place for developers to get extra information.(yes todo notes now show up in the "Warning" tab. But I'm not convinced this is the right place for them)

 Context: When a merge is performed and copy/paste is detected, the system should notify the user immediately. This notification is crucial so the developer understands that the original reference will be lost in subsequent environments — TST, HMG, PPRD, and PRD — with production being the most critical. Entity Risk: Data Loss : Copy/paste can overwrite or eliminate important references, leading to inconsistencies and missing information. Process Impacted : Suspension of Active Processes : Losing references may interrupt workflows or cause unexpected behavior in critical environments. Current Problem : At present, the merge process does not provide a clear “red alert” warning when this situation occurs. As a result, unaware/new developers may unintentionally commit this error, causing data loss and instability. Proposed Improvement: Preventive Alert System Automatically detect copy/paste during merge. Display a high-visibility warning (e.g., “⚠️ Warning: Original reference will be lost”). Developer Awareness & Accountability Require explicit confirmation before allowing the merge to proceed. Log the incident for traceability and quality assurance. Benefits Prevents data loss across environments. Improves system reliability in production. Ensures developers are fully aware of the consequences before committing changes.

When there is an error, like missing reference, at the beginning of solution publish - it still continues to go for half an hour or more, and only after "Gathering dependencies..." stage it fails with a message like "The deployment was aborted due to errors. No applications or modules were deployed".This is really really really frustrating, especially when you are in a hurry, especially when you have noticed the error and fixed it, but you still have to wait for half an hour because there is no way to stop solution publish.Why would it not stop immediately after the fatal error has occurred? Or at least show  that "continue/abort" confirmation, immediately.Isn't this rule #2 from The Book?

Add an auto-checker tool that verifies the app against best security practices before deployment.

Would be great if we could see progress of publishing into taskbar just like it happens in chrome when we download some file.

Currently, Neo AI actively participates in OutSystems Forums and has already provided 22 accepted solutions, showcasing its ability to deliver valuable guidance to developers. Building on this capability, Neo AI can be extended to act as a Virtual User Group Host/Organizer. In this role, Neo AI would: Automate Event Scheduling: Based on speaker availability and requests, Neo AI can create and schedule virtual user group sessions. Host & Moderate Sessions: Neo AI could act as a co-host, handling introductions, sharing agendas, moderating Q&A, and even summarizing discussions. Personalized Recommendations: Suggest relevant topics, speakers, or sessions for attendees based on their forum activities and interests. Knowledge Archiving: Automatically generate and publish session notes, recordings, and highlights for the community. Regards Murali

The AI Mentor currently provides visibility into 'Unused Actions in Modules' and 'Unused Aggregates or SQL Queries'. Similarly, introducing a feature to identify 'Unused APIs' would greatly benefit developers by enabling them to efficiently manage their APIs, thereby mitigating potential security risks.

When using the BottomSheet OutSystemsUI pattern I keep missing the option of clicking on the overlay to close the sheet. We can of course develop custom javascript to do that, but it would be better to include an option in this pattern.

Context-aware logic suggestions, error fixes, and performance tips using AI. Smart autocomplete for expressions and logic flows.

There is a limitation in OutSystems Service Studio where folders cannot be nested inside other folders. As a result, application elements must be kept in a flat structure, which reduces clarity, organization, and long-term maintainability. Why not allow developers the flexibility to create a better and more structured folder management system?