It would be great if OutSystems could collaborate with partner companies to offer internship opportunities for newcomers in the community. While the OutSystems Developer School already helps many beginners learn the platform, having a structured internship program would give them valuable real-world experience and a chance to apply their knowledge in live projects. Through this initiative, OutSystems could also recommend top-performing learners or certified developers to partner companies, helping new talents get recognized and boosting their confidence to grow further in their OutSystems careers.

It would be great if OutSystems could provide its own AI solution, similar to Neo, to help developers implement AI-driven features securely within the platform. Relying on third-party AI integrations often raises concerns about data privacy and security. By offering a native OutSystems AI, customers would gain greater confidence that their data remains protected while still benefiting from AI capabilities such as automation, prediction, and chat-based assistance all managed securely within the OutSystems ecosystem.

It would be really good to have a list of all unconsumed public elements from a producer module.This would be of great help in 2 scenarios:- while review code from other developers- while working on an application that was developed by other teamsIt is very common that code gets developed with a purpose in mind, but somewhere down the line it becomes obsolete or ends up not being needed. If teams are not methodic, a lot of unused public elements end-up bloating up the module. I am currently working on a project developed during 2 years by another company. I constantly find unused public elements all over the place. They obviously are obsolete, and if my team needs some of that functionality, most likely we will develop from scratch rather than have to search if some code exists for the purpose we need. Hence, unconsumed elements are as pure trash on the application. But there is no way to make a bulk clean up. It would be great to be all to see a full list without having to go one by one.

Hello OutSystems Community, Building on the theme of making Application Objects (AOs) more visible in the Forge, I have another simple but powerful suggestion. The Problem: When we search for assets, the results page shows a list of component "cards." Each card displays useful info like ratings and download counts. However, to see the AO count, a critical piece of information for assessing impact and cost, we must click to open the asset's detail page. My Idea: My proposal is to display the AO count directly on the asset card in the search results list. This could be a small and clean UI element, perhaps next to the download or rating indicators. It would give us immediate, at-a-glance information for every component on the page. For example, the card could look something like this: [Asset Name] Rating: ★★★★★ (25) Downloads: 2.5k AOs: 8 <-- New information here Benefits: Instant Comparison: Allows developers to immediately compare the AO "weight" of different components without ever leaving the search results page. Improved User Experience: Reduces clicks and streamlines the workflow for finding the right asset, making the Forge much more efficient to browse. Works Perfectly with Filters: This visual aid would be a perfect companion to an AO filtering feature. We could filter for a range (e.g., 1-20 AOs) and then instantly see the precise count for each result to make the best choice. This small UI enhancement would have a huge positive impact on our daily workflow in the Forge. Thanks for your consideration.

Provide the ability to set the extended properties on reactive emails in the same way they are available in traditional. There is currently no way to set extended properties on reactive emails, this currently means we will have technical debt in maintaining an secondary application purely to send emails to enable setting importance, out of office suppression, expiry etcThe following is an example of the traditional extended properties in a traditional emailThe above is used to suppress out of office messages for mailings and prevents a deluge of out of office responses when a number of emails are sent.Importance is set on some emails based on the business process being followed e.g. high risk/value the importance can be set to High and the email client shows the importance of the email.The extended properties on the email has solved a number of issues with email visibility in a users inbox by adding the relevant property e.g. importance, sensitivity and also expiry has meant that processes that do rely on an email get the relevant attention required.

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.

Just like in Traditional Web, it would be nice to have a simple way of translation prompts/text/static entities.

With the introduction of the Dynamic Case Management Framework, OutSystems advocates to use GUID as a unique Text Identifier (see https://success.outsystems.com/Documentation/Case_Management/Create_a_case_management_app ).Apart from that GUID as identifiers have some other use cases too:Less "hackable" URLs to your application pages than when using Integer IdentifiersLess meaningful Identifiers (Employee number 2 is probably longer with the company than Employee number 58)You want the data to be uniquely-identified, no matter where it came from.You need to be able to combine data from difference sources with little-to-no chance of duplicate GUIDs.Furthermore, you don't want or don't care about the users needing to remember an ID themselvesIt would be nice if there is more support in the Platform:Add a new datatype called GUID, with an AutoNumber option.Add a popup menu option to generate a GUID and set it as a string literal for any attribute of datatype GUIDAdd built-in feature to also generate a GUID for Mobile and Reactive, as it is currently only available server side. Yes Forge component exists to help you, but this should be build in.

Allow "Dark mode" on New Service Center

Hello OutSystems community, I have a suggestion that I believe could significantly improve security in our applications developed on the platform. Currently, when passing parameters via URL, these parameters can be easily visible and even manipulated by malicious users. This can represent a significant vulnerability, especially when these parameters contain sensitive information such as user IDs, authentication tokens, among others. My proposal is to implement a functionality that allows marking input parameters on a screen as "Encrypted". When a parameter is marked as such, the value of this parameter would be automatically encrypted in the URL before being sent to the server. This approach would provide an additional layer of security, making it more difficult for malicious third parties to view or manipulate sensitive data transmitted through URLs. I would like to hear the community's opinion on this idea and whether it would be feasible to implement it on the OutSystems platform.