Currently, when we end a screen action, it is possible to end it with a destination widget, open a new screen, in the same tab.It would be great a new option in this widget that, when set as true, it would open the new screen in a new tab.

Add an option in the Service Studio settings to disable automatic joins when adding new entities to aggregates. This is useful when there are multiple possible automatic joins. In many cases, fixing an incorrect join requires more effort than benefiting from the automatic behavior. Additionally, in more complex aggregates with many joins, it becomes harder to manage and verify which joins were automatically added and whether other entities were also included automatically.

It would be relevant for us to be able to manage our certificates, to be able to remove expired ones to avoid conflicts on the platform, and to be able to renew certificates when emergencies arise. Having a view of our certificates without having to open tickets, and we end up wasting time trying to understand the problems, however I emphasize that the OutSystems team is 5-star. Or a lifetime option for access this information.

Dropdown search widget required default mandatory validation message. Need to add validation message and Mandatory message in Dropdown search widget. Developer and Front-end users will get benefits.

As requested by OutSystems Support Team, I am creating this Idea because it's important that the build log for any compilation on mobile on ODC be similiar to what we have in O11. Today, the mobile build is a huge amount of text that can be difficult to understand what is the main reason your mobile app is not compiling. In O11, it's more easy to understand. Maybe on ODC, put the main error on the top (or at the end) of the file so the developer can easily identify the root cause of the APK/IPA being broken upon compilation.

When creating an application with Mentor, I would like to see the effective creation of business processes (BPMs), because in tests, in the requirement document that Mentor read, it has the BPM rules but it seems that it has not yet been implemented.

In OutSystems, each Email Web Screen is counted as an Application Object (AO), and AOs directly impact licensing cost. In many enterprise applications, we create multiple Email-related Web Screens (for templates, preview, configuration, triggers, admin panels, etc.), which can significantly increase the AO count. My idea is to replace most Email Web Screens with an Extension-based approach. Instead of building multiple Web Screens for email management, we can: Handle email generation, templates, and logic inside an Extension Store email templates and configurations in the database Trigger emails via server actions or APIs without requiring dedicated UI screens How this helps customers: ✅ Reduces AO consumption by eliminating multiple Email Web Screens ✅ Lowers licensing cost for large-scale applications ✅ Centralized email logic in one reusable Extension ✅ Better performance and maintainability for complex email workflows ✅ Reusable across multiple modules and applications Example Use Cases: Transactional emails (OTP, notifications, approvals) Bulk marketing or system alerts Multi-tenant email templates per client Configurable email rules without UI-heavy admin screens This approach can help enterprises optimize licensing cost while still keeping email functionality flexible and scalable.

In an Outsystems project we find ourselves building in an application in the middle of a landscape where communication with web services is not always there. This situation makes it very difficult to test a complete flow since dependencies of other systems are quite often down.In order to surpass this situation making the application more independent for testing purposes, the idea is to try to have a module with a mock of those services and just changing the entry point on DEV / TST environment to make it work.The problem is the external parties' web services have hyphens ("-") on the URL path of the web methods and when we are creating the mock service to expose, Service Studio considers the "-" an illegal character.

So you don't accidentally publish a full solution on your production environment, thinking you're on DEV. It could be taken a step forward, by changing Service Studio's menu color to the one of the Service Center it's connected to.

One of the purposes of publishing a solution, is to refresh all modules in it, and reflect a change of an upgrade. What I propose, is to remove unused dependencies between the defined modules in the solution. I recommend for it to a configurable option. But it would be helpful especially in big projects, where the architecture is big and complicated. Also, it could be a helpful option before checking the architecture in Discovery. Before the check we have all modules refreshed, and all unnecessary links broken.