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.

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.

As we know, contact centres are underwater everywhere (as SNS24 in Portugal).The idea is to create a chatbot for FAQs that allow people to quickly get relevant information.We can use OutSystems.AI chatbot , integrated with the QnA service and integrated with some oficial knowledge bases (example: https://www.ecdc.europa.eu/en/novel-coronavirus-china/questions-answers ).Unanswered questions can be listed in a page, to be reviewed and added to the knowledge base, to make the chatbot smarter and smarter.The chatbot could then be highly improved if we allow humans to enter the loop and make the experience even smoother.

I would be great to be able to edit entity data (in addition to the ViewData functionality) inside Service Studio.As far as I know, there is no easy way to manually edit data for testing purposes.This is extremely helpful especially when bootstrapping data from Excel

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!

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.

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.

This looks more like a bug, but as per requested by the Support team here the details: Apparently, containing special chars like : in the URL is problematic. For example, for the official Google Maps Routes API Endpoint: "/directions/v2 : computeRoutes", although set correctly and accepted in the URL Path in Service Studio: the path is still being read in runtime as: "/directions/v2 %3A computeRoutes" by ODC/Outsystems 11. Current workaround works to explicitly decode the URL in the OnBeforeRequest: However, since the platform allows special chars in the URL path in a REST Action and doesn't complain or notify, it does not seem right and would make a better UX whilst saving time to another developers like me in future to figure out what's the issue, how to solve and then implement.

Inside an aggregate comparing the same variable (inside a filter) should trigger a warning. If an aggregate filter says user.id=user.id it should trigger a warning clearly this will always be true. the user would have likely meant user.id=userid