To prevent an agent from accidently executing multiple times without supervision. It would be good to add a security feature to disable specific agents on the ODC Portal for each environment.

Most of the times server actions, client actions can have multiple branches. While debugging each node is currently available it would save a lot of time if we could just hit continue and the app automatically highlights the full path the execution has traversed. The Idea is to have like a highlighted flow in the server actions, client actions, data actions etc. where developers can see exactly which flow the execution is going wrong in and make fixes accordingly. This would help debug faster, saving the time to actually understand what each node is doing and also understanding the logic on a broader level.

While OutSystems UI provides a solid foundation for functionality, the default Layouts (Top Menu, Side Menu, etc.) and screen templates have started to feel a bit dated compared to modern web standards (e.g., Vercel, Stripe, modern SaaS dashboards). Currently, frontend developers spend a significant amount of time overriding default CSS, adjusting padding, shadows, and font hierarchies to make applications look "fresh" and less like a standard enterprise tool. The Idea: I propose introducing a new set of "Modern" Layouts and Themes within OutSystems UI that prioritize current design trends out-of-the-box. What this should include: Cleaner Aesthetics: More generous whitespace, softer shadows, and modern border-radius defaults. Updated Navigation: Sidebar and Topbar designs that feel more like modern SaaS products (e.g., collapsible floating menus, blurred/glassmorphism backgrounds). Typography Focus: Better default font scaling and hierarchy for readability. Native Dark Mode Polish: Improved contrast ratios for the default dark mode. The Benefit: Faster Time-to-Market: Developers won't need to waste time writing custom CSS just to make the app look modern. Better Sales PoCs: Out-of-the-box apps will look impressive immediately, helping sell the platform to UI-conscious clients. Developer Experience: A more inspiring starting point for UI design. Let’s give OutSystems applications a fresh coat of paint by default!

I would like to propose the development of an API that allows integration with CI/CD tools to check for unused dependencies in an application. This API would provide a boolean value indicating whether there are any unused dependencies, enabling automatic detection during the CI/CD pipeline. By integrating this API into the CI/CD workflow, developers can easily identify and remove unnecessary dependencies, improving application performance and reducing resource consumption early in the development process.

For many times we need to check the history of changes to an action or screen, it is also interesting to compare with an earlier version. It would work with the following steps:1 - Click the right mouse button2 - Select the option to view the history3 - View the history with the name, modification date and an option to compare with the current version.Images1 - Option to view history2 - History window with the option to compare with previous versions

Hello, It once existed... but it doesn't anymore. https://www.outsystems.com/ideas/1673/bundling-and-minifying-the-javascript-css-files/ When we publish a solution that has a mechanism to minifying CSS and JS - well, it could be a checkbox that the user chooses whether or not they want this option, and it might not be available in the free version... But that could benefit the performance of applications.

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.

When changing locale of a screen, in multi-lingual applications, everything is translated, except validation messages. The validation message is displayed in the right locale when triggered, however, if the validation message was already added, and then the locale changes, the validation messages are not translated to match the new locale. To translate the validation messages, the user has to trigger the form validation again.

I the Rest configuration in Service Center should have the same fields that are in Service Studio. When I configure the Authentication in Service Studio appear the field Scopes But in Service Center this field doesn't exist You should have the same fields in both places

A mobile application that allows developers to join User Group events anytime, even when they don’t have their laptop. This makes event participation easier, increases accessibility, and encourages more developers to attend and learn from OutSystems community sessions.